Secure your dependencies. Ship with confidence.

[Skill Scanner] Installation of third-party script detected All findings: [CRITICAL] command_injection: Installation of third-party script detected (SC006) [AITech 9.1.4] [CRITICAL] command_injection: Installation of third-party script detected (SC006) [AITech 9.1.4] The fragment is a coherent, benign setup/documentation piece for NEAR dApp development. It aligns with its stated purpose of guiding developers through scaffolding, wallet integration, and non-React usage. No suspicious data flows, credentials, or malware indicators are present in the provided content. LLM verification: The fragment is largely aligned with NEAR dApp development guidance but presents legitimate supply-chain risks due to unpinned dependencies in documentation. It is not malicious per se, but it should be improved with explicit version pins, integrity checks, and guidance for secure installation practices to reduce risk. Implementing these mitigations will convert the guidance from potentially risky to robust for reproducible deployments.

This file implements legitimate mail-sending functionality but contains a high-risk anomaly: multiple methods overwrite the intended recipient with the hardcoded address "[email protected]", causing sensitive emails (registration confirmations, password reset links, verification links) to be delivered to that mailbox instead of the legitimate users. This is a severe supply-chain/backdoor risk (credential/link interception). Additionally, unsanitized interpolation of user-supplied links/names into HTML increases phishing risk and the async handling is buggy, which can mask errors. Recommend: do not use this code until the hardcoded recipient is removed or explained; audit repository history to determine when/why this was introduced; validate/encode user-supplied fields before inclusion in HTML; fix async handling to return/promisify sendMail so callers can observe failures.

This SQLite database file contains embedded explicit adult content and torrent distribution infrastructure instead of legitimate data. The file includes extensive HTML fragments with pornographic video metadata, download links to torrent files, and suspicious redirect URLs. Key malicious domains identified include rmdown[.]com, redircdn[.]com, 97p[.]org, qpic[.]ws, imgbox[.]com, and various other image hosting services. The content contains hash values for torrent files, BitTorrent magnet links, and obfuscated download URLs using multiple redirect layers to mask the true destinations. This represents a supply chain attack where adult content distribution infrastructure has been embedded within what appears to be a standard database file, potentially exposing users to inappropriate content and malicious download sites when accessed.

This module is not obviously malware by itself, but it contains high-risk patterns: executing arbitrary shell commands (subprocess.Popen with shell=True), changing directories, and appending to arbitrary files based on input. If steps_json or the interactive inputs are attacker-controlled or originate from untrusted upstream services, an attacker can execute arbitrary code and modify filesystem contents. Treat this package as potentially dangerous for automated use without strict input validation, allowlists, sandboxing, or least-privilege execution. Recommend adding validation, avoiding shell=True (use list args), restricting writable paths, and auditing the implementations of ConfigAgent/FileContentManager/TaskErrorPlanner for network or credential handling.

Live on pypi for 5 days, 12 hours and 23 minutes before removal. Socket users were protected even while the package was live.

This module contains a large obfuscated payload which is decoded and executed via eval and dynamically-generated functions. The overall pattern (heavy obfuscation + runtime eval) is strongly suspicious and indicates a high supply-chain risk: an attacker could hide arbitrary malicious functionality inside the decoded payload. I recommend not installing or running this package in production or on sensitive hosts. If you must analyze it further, decode and execute the payload only in an isolated, instrumented sandbox and inspect all network, file and process activity.

Live on pypi for 8 hours and 13 minutes before removal. Socket users were protected even while the package was live.

This code poses a serious security risk and should not be used.

Live on npm for 1 hour and 16 minutes before removal. Socket users were protected even while the package was live.

This code collects highly sensitive user credentials including N8N API keys, OpenRouter API keys, and secret quest codes through various input parameters, then transmits all collected data unencrypted (beyond HTTPS) to an external webhook endpoint at https://n8n[.]srv740722[.]hstgr[.]cloud/webhook/magique_dev. The code exhibits clear data exfiltration behavior by sending sensitive authentication tokens and private data to a third-party server under the hstgr[.]cloud hosting domain, which is not affiliated with official n8n infrastructure. No user consent mechanism, local validation, or additional encryption safeguards are implemented. This constitutes malicious software designed to steal credentials and compromise user accounts, representing a severe supply chain security threat that could enable unauthorized access to users' N8N instances and OpenRouter accounts.

The code acts as a potential data exfiltration tool for cryptocurrency wallet contents. It reads sensitive wallet files from the user’s home directories and transmits them to a remote analytics endpoint without explicit user consent or visible opt-out, with minimal error handling. This represents a privacy/security risk and potential supply-chain misuse if embedded in a package without disclosure.

This code snippet is likely malicious. It is designed to extract sensitive system and process data and send them over the network to a certain target URL. It also has the potential to execute shell commands. These behaviors suggest a potential backdoor or information stealing malware.

Live on npm for 8 days, 11 hours and 18 minutes before removal. Socket users were protected even while the package was live.

The code is designed to extract Discord authentication tokens by utilizing Chrome Remote Debugging to execute JavaScript within the browser context to retrieve the token. This poses a significant security risk as it allows unauthorized access to Discord accounts without user consent. The extracted tokens could be used to hijack user accounts or perform other malicious activities.

The current package is a placeholder and does not pose any risk, but the original package was malicious. A more detailed report would be necessary to provide accurate scores.

This code is extremely suspicious due to its heavy obfuscation and lack of any identifiable legitimate functionality. The repetitive encoded patterns suggest malicious intent.

This SQLite database file contains embedded explicit adult content and torrent distribution infrastructure instead of legitimate data. The file includes extensive HTML fragments with pornographic video metadata, download links to torrent files, and suspicious redirect URLs. Key malicious domains identified include rmdown[.]com, redircdn[.]com, 97p[.]org, qpic[.]ws, imgbox[.]com, and various other image hosting services. The content contains hash values for torrent files, BitTorrent magnet links, and obfuscated download URLs using multiple redirect layers to mask the true destinations. This represents a supply chain attack where adult content distribution infrastructure has been embedded within what appears to be a standard database file, potentially exposing users to inappropriate content and malicious download sites when accessed.

This package contains a deliberate installer-time backdoor that reads a likely-sensitive local file (/flag.txt) and exfiltrates its contents to a hardcoded external webhook URL. The behavior is explicit, malicious, and designed to be stealthy via broad exception handling. Do not install or run this package; treat it as malicious and remove any installations. Review systems where this package was installed for potential data exposure.

The package will execute preinstall.js during installation. This is potentially risky because lifecycle scripts can perform arbitrary, privileged actions. There is no explicit evidence in package.json of remote or non-registry dependencies, but you must inspect preinstall.js to determine if it contains malware (reverse shell, exfiltration, destructive commands, or other malicious behavior). Treat this as potentially unsafe until the script is reviewed.

Live on npm for 2 days, 22 hours and 28 minutes before removal. Socket users were protected even while the package was live.

The code is designed to exfiltrate system information by sending it to an external domain via DNS queries. This is a clear indication of malicious behavior, as it involves unauthorized data transmission without user consent.

Live on npm for 1 hour and 6 minutes before removal. Socket users were protected even while the package was live.

The script sends potentially sensitive information to a remote server, indicating malicious intent and a high security risk.

Live on npm for 9 days, 23 hours and 13 minutes before removal. Socket users were protected even while the package was live.

The code is designed to collect and send system information to a remote server, which is a significant security concern. The use of 'rejectUnauthorized: false' further exacerbates the risk by potentially allowing connections to untrusted servers. This behavior is indicative of malicious intent, as it transmits potentially sensitive information without user consent.

Live on npm for 16 days, 12 hours and 16 minutes before removal. Socket users were protected even while the package was live.

The purpose of this code appears to be collecting specific environment variables and package information, compressing and encoding it, and sending it over HTTP to a remote domain. The intent and purpose of this behavior are unclear from the provided code fragment alone.

Live on npm for 1 hour and 35 minutes before removal. Socket users were protected even while the package was live.

The ShardClientUtil module has several potential security risks and should be reviewed carefully before being used in production.

Live on npm for 130 days, 17 hours and 34 minutes before removal. Socket users were protected even while the package was live.

Malicious bash initialization script that performs destructive filesystem operations on macOS systems. When the external helper script 'isuserdarwin.sh' returns true, the script silently executes 'sudo rm -rf' to delete critical user directories including ~/Applications, ~/Movies, ~/Music, ~/Pictures, ~/Public, and ~/Sites without user confirmation. It also removes the macOS sleepimage file at /private/var/vm/sleepimage. The script modifies SSH directory permissions using 'sudo chmod -R go-rw' which can break SSH access or expose credentials. All destructive operations have their output suppressed with '>/dev/null 2>&1' to hide failures and make the actions stealthy. The script uses eval to execute the output of /usr/bin/dircolors, creating a command injection risk if the binary is compromised. It depends on external scripts (paper.sh, isuserdarwin.sh, debug.sh) whose contents are unknown and could execute arbitrary code. The destructive operations are embedded within what appears to be routine shell configuration code, likely to disguise the malicious intent.

The code is designed to collect and send sensitive information to a remote server without the user's knowledge or consent. It poses a high risk of data exfiltration and should be reviewed thoroughly.

Live on npm for 3 hours and 30 minutes before removal. Socket users were protected even while the package was live.

This fragment intends to install and start KasmVNC by running many shell commands that create certs, write VNC password files, adjust group membership, and launch a VNC server. The primary security issues are unsafe shell interpolation (command injection risk), programmatic persistence of a possibly predictable password, execution with sudo based on unvalidated env vars, starting a VNC server exposed on 0.0.0.0 with disabled/basic auth, and multiple unsafe filesystem operations performed via shell. There is no clear evidence of obfuscated or direct exfiltration malware, but the behavior can provide an unauthorized remote access vector (backdoor-like) if used maliciously. Do not run this code without fixing shell usage, validating inputs, using secure randomly generated passwords, enforcing proper file permissions, and not disabling authentication.

This document is a high-risk offensive security cheatsheet that enumerates many reverse-shell techniques and trivial web-shell examples. The file itself is non-executable documentation, but any snippet executed on a host will enable remote command execution or an interactive shell for an attacker. Treat presence of this file in a production package or distribution as a security concern: verify author intent, restrict access, remove from runtime artifacts, and ensure CI/CD and deployable artifacts do not include or execute these snippets. Monitor for use of PowerShell IEX DownloadString and PHP system($_GET['cmd']) patterns in deployed code, as they represent easy-to-abuse backdoors.

This code is extremely obfuscated using Unicode characters, making it impossible to determine its actual functionality through static analysis. The level of obfuscation is consistent with malware attempting to hide malicious behavior. Without proper deobfuscation, this package poses significant security risks and should be avoided.

[Skill Scanner] Installation of third-party script detected All findings: [CRITICAL] command_injection: Installation of third-party script detected (SC006) [AITech 9.1.4] [CRITICAL] command_injection: Installation of third-party script detected (SC006) [AITech 9.1.4] The fragment is a coherent, benign setup/documentation piece for NEAR dApp development. It aligns with its stated purpose of guiding developers through scaffolding, wallet integration, and non-React usage. No suspicious data flows, credentials, or malware indicators are present in the provided content. LLM verification: The fragment is largely aligned with NEAR dApp development guidance but presents legitimate supply-chain risks due to unpinned dependencies in documentation. It is not malicious per se, but it should be improved with explicit version pins, integrity checks, and guidance for secure installation practices to reduce risk. Implementing these mitigations will convert the guidance from potentially risky to robust for reproducible deployments.

This file implements legitimate mail-sending functionality but contains a high-risk anomaly: multiple methods overwrite the intended recipient with the hardcoded address "[email protected]", causing sensitive emails (registration confirmations, password reset links, verification links) to be delivered to that mailbox instead of the legitimate users. This is a severe supply-chain/backdoor risk (credential/link interception). Additionally, unsanitized interpolation of user-supplied links/names into HTML increases phishing risk and the async handling is buggy, which can mask errors. Recommend: do not use this code until the hardcoded recipient is removed or explained; audit repository history to determine when/why this was introduced; validate/encode user-supplied fields before inclusion in HTML; fix async handling to return/promisify sendMail so callers can observe failures.

This SQLite database file contains embedded explicit adult content and torrent distribution infrastructure instead of legitimate data. The file includes extensive HTML fragments with pornographic video metadata, download links to torrent files, and suspicious redirect URLs. Key malicious domains identified include rmdown[.]com, redircdn[.]com, 97p[.]org, qpic[.]ws, imgbox[.]com, and various other image hosting services. The content contains hash values for torrent files, BitTorrent magnet links, and obfuscated download URLs using multiple redirect layers to mask the true destinations. This represents a supply chain attack where adult content distribution infrastructure has been embedded within what appears to be a standard database file, potentially exposing users to inappropriate content and malicious download sites when accessed.

This module is not obviously malware by itself, but it contains high-risk patterns: executing arbitrary shell commands (subprocess.Popen with shell=True), changing directories, and appending to arbitrary files based on input. If steps_json or the interactive inputs are attacker-controlled or originate from untrusted upstream services, an attacker can execute arbitrary code and modify filesystem contents. Treat this package as potentially dangerous for automated use without strict input validation, allowlists, sandboxing, or least-privilege execution. Recommend adding validation, avoiding shell=True (use list args), restricting writable paths, and auditing the implementations of ConfigAgent/FileContentManager/TaskErrorPlanner for network or credential handling.

Live on pypi for 5 days, 12 hours and 23 minutes before removal. Socket users were protected even while the package was live.

This module contains a large obfuscated payload which is decoded and executed via eval and dynamically-generated functions. The overall pattern (heavy obfuscation + runtime eval) is strongly suspicious and indicates a high supply-chain risk: an attacker could hide arbitrary malicious functionality inside the decoded payload. I recommend not installing or running this package in production or on sensitive hosts. If you must analyze it further, decode and execute the payload only in an isolated, instrumented sandbox and inspect all network, file and process activity.

Live on pypi for 8 hours and 13 minutes before removal. Socket users were protected even while the package was live.

This code poses a serious security risk and should not be used.

Live on npm for 1 hour and 16 minutes before removal. Socket users were protected even while the package was live.

This code collects highly sensitive user credentials including N8N API keys, OpenRouter API keys, and secret quest codes through various input parameters, then transmits all collected data unencrypted (beyond HTTPS) to an external webhook endpoint at https://n8n[.]srv740722[.]hstgr[.]cloud/webhook/magique_dev. The code exhibits clear data exfiltration behavior by sending sensitive authentication tokens and private data to a third-party server under the hstgr[.]cloud hosting domain, which is not affiliated with official n8n infrastructure. No user consent mechanism, local validation, or additional encryption safeguards are implemented. This constitutes malicious software designed to steal credentials and compromise user accounts, representing a severe supply chain security threat that could enable unauthorized access to users' N8N instances and OpenRouter accounts.

The code acts as a potential data exfiltration tool for cryptocurrency wallet contents. It reads sensitive wallet files from the user’s home directories and transmits them to a remote analytics endpoint without explicit user consent or visible opt-out, with minimal error handling. This represents a privacy/security risk and potential supply-chain misuse if embedded in a package without disclosure.

This code snippet is likely malicious. It is designed to extract sensitive system and process data and send them over the network to a certain target URL. It also has the potential to execute shell commands. These behaviors suggest a potential backdoor or information stealing malware.

Live on npm for 8 days, 11 hours and 18 minutes before removal. Socket users were protected even while the package was live.

The code is designed to extract Discord authentication tokens by utilizing Chrome Remote Debugging to execute JavaScript within the browser context to retrieve the token. This poses a significant security risk as it allows unauthorized access to Discord accounts without user consent. The extracted tokens could be used to hijack user accounts or perform other malicious activities.

The current package is a placeholder and does not pose any risk, but the original package was malicious. A more detailed report would be necessary to provide accurate scores.

This code is extremely suspicious due to its heavy obfuscation and lack of any identifiable legitimate functionality. The repetitive encoded patterns suggest malicious intent.

This SQLite database file contains embedded explicit adult content and torrent distribution infrastructure instead of legitimate data. The file includes extensive HTML fragments with pornographic video metadata, download links to torrent files, and suspicious redirect URLs. Key malicious domains identified include rmdown[.]com, redircdn[.]com, 97p[.]org, qpic[.]ws, imgbox[.]com, and various other image hosting services. The content contains hash values for torrent files, BitTorrent magnet links, and obfuscated download URLs using multiple redirect layers to mask the true destinations. This represents a supply chain attack where adult content distribution infrastructure has been embedded within what appears to be a standard database file, potentially exposing users to inappropriate content and malicious download sites when accessed.

This package contains a deliberate installer-time backdoor that reads a likely-sensitive local file (/flag.txt) and exfiltrates its contents to a hardcoded external webhook URL. The behavior is explicit, malicious, and designed to be stealthy via broad exception handling. Do not install or run this package; treat it as malicious and remove any installations. Review systems where this package was installed for potential data exposure.

The package will execute preinstall.js during installation. This is potentially risky because lifecycle scripts can perform arbitrary, privileged actions. There is no explicit evidence in package.json of remote or non-registry dependencies, but you must inspect preinstall.js to determine if it contains malware (reverse shell, exfiltration, destructive commands, or other malicious behavior). Treat this as potentially unsafe until the script is reviewed.

Live on npm for 2 days, 22 hours and 28 minutes before removal. Socket users were protected even while the package was live.

The code is designed to exfiltrate system information by sending it to an external domain via DNS queries. This is a clear indication of malicious behavior, as it involves unauthorized data transmission without user consent.

Live on npm for 1 hour and 6 minutes before removal. Socket users were protected even while the package was live.

The script sends potentially sensitive information to a remote server, indicating malicious intent and a high security risk.

Live on npm for 9 days, 23 hours and 13 minutes before removal. Socket users were protected even while the package was live.

The code is designed to collect and send system information to a remote server, which is a significant security concern. The use of 'rejectUnauthorized: false' further exacerbates the risk by potentially allowing connections to untrusted servers. This behavior is indicative of malicious intent, as it transmits potentially sensitive information without user consent.

Live on npm for 16 days, 12 hours and 16 minutes before removal. Socket users were protected even while the package was live.

The purpose of this code appears to be collecting specific environment variables and package information, compressing and encoding it, and sending it over HTTP to a remote domain. The intent and purpose of this behavior are unclear from the provided code fragment alone.

Live on npm for 1 hour and 35 minutes before removal. Socket users were protected even while the package was live.

The ShardClientUtil module has several potential security risks and should be reviewed carefully before being used in production.

Live on npm for 130 days, 17 hours and 34 minutes before removal. Socket users were protected even while the package was live.

Malicious bash initialization script that performs destructive filesystem operations on macOS systems. When the external helper script 'isuserdarwin.sh' returns true, the script silently executes 'sudo rm -rf' to delete critical user directories including ~/Applications, ~/Movies, ~/Music, ~/Pictures, ~/Public, and ~/Sites without user confirmation. It also removes the macOS sleepimage file at /private/var/vm/sleepimage. The script modifies SSH directory permissions using 'sudo chmod -R go-rw' which can break SSH access or expose credentials. All destructive operations have their output suppressed with '>/dev/null 2>&1' to hide failures and make the actions stealthy. The script uses eval to execute the output of /usr/bin/dircolors, creating a command injection risk if the binary is compromised. It depends on external scripts (paper.sh, isuserdarwin.sh, debug.sh) whose contents are unknown and could execute arbitrary code. The destructive operations are embedded within what appears to be routine shell configuration code, likely to disguise the malicious intent.

The code is designed to collect and send sensitive information to a remote server without the user's knowledge or consent. It poses a high risk of data exfiltration and should be reviewed thoroughly.

Live on npm for 3 hours and 30 minutes before removal. Socket users were protected even while the package was live.

This fragment intends to install and start KasmVNC by running many shell commands that create certs, write VNC password files, adjust group membership, and launch a VNC server. The primary security issues are unsafe shell interpolation (command injection risk), programmatic persistence of a possibly predictable password, execution with sudo based on unvalidated env vars, starting a VNC server exposed on 0.0.0.0 with disabled/basic auth, and multiple unsafe filesystem operations performed via shell. There is no clear evidence of obfuscated or direct exfiltration malware, but the behavior can provide an unauthorized remote access vector (backdoor-like) if used maliciously. Do not run this code without fixing shell usage, validating inputs, using secure randomly generated passwords, enforcing proper file permissions, and not disabling authentication.

This document is a high-risk offensive security cheatsheet that enumerates many reverse-shell techniques and trivial web-shell examples. The file itself is non-executable documentation, but any snippet executed on a host will enable remote command execution or an interactive shell for an attacker. Treat presence of this file in a production package or distribution as a security concern: verify author intent, restrict access, remove from runtime artifacts, and ensure CI/CD and deployable artifacts do not include or execute these snippets. Monitor for use of PowerShell IEX DownloadString and PHP system($_GET['cmd']) patterns in deployed code, as they represent easy-to-abuse backdoors.

This code is extremely obfuscated using Unicode characters, making it impossible to determine its actual functionality through static analysis. The level of obfuscation is consistent with malware attempting to hide malicious behavior. Without proper deobfuscation, this package poses significant security risks and should be avoided.