Secure your dependencies. Ship with confidence.

This module contains explicit remote code execution behaviors: an immediate shell command executed at module import and an unsanitized execution sink that runs arbitrary shell commands from runtime input. The top-level side-effect is a severe supply-chain issue; the execute method provides straightforward RCE for any caller controlling the 'command' parameter. Treat this package as malicious/untrusted and avoid importing or running it. If encountered in your dependency tree, remove it and investigate any environments where it was installed or loaded.

The improved assessment identifies a high-risk pattern in the Node path of the XMLHttpRequest polyfill: it dynamically writes a script to disk, spawns a process to execute it, and then cleans up. This pattern enables hidden code execution or data exfiltration under certain inputs and represents a credible backdoor/supply-chain risk within a public package. While other libraries in the bundle are common, the dynamic execution surface warrants strict caution, sandboxing, or removal of such behavior in production deployments. Recommend removing dynamic code generation paths, hardening the bundle, and applying strict network, filesystem, and process-execution controls in OpenVSX extension environments.

The code exhibits malicious behavior by exfiltrating sensitive system and project data to external servers without user consent. The presence of an infinite loop and the nature of the data being sent raises significant security concerns.

Live on npm for 54 minutes before removal. Socket users were protected even while the package was live.

The code demonstrates clear malicious behavior by collecting and attempting to exfiltrate system information. The obfuscation further indicates an attempt to conceal this behavior, warranting high scores in malware, obfuscation, and risk categories.

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

This module implements a remote-driven automation CLI that will execute arbitrary shell commands returned by the remote API and return command outputs/errors back to that API. The most serious risks are: (1) remote-to-local arbitrary command execution without whitelisting or sandboxing, and (2) exfiltration of command outputs back to the remote service. Hard-coded API key persisted to disk and a persistent HOST_ID increase credential/identification risk and tracking. The code appears intended for remote automation rather than containing an obvious hidden backdoor, but its design choices create a substantial supply-chain and remote-execution risk. Recommend not running this on sensitive hosts, removing embedded keys, adding strict client-side validation/whitelisting and explicit user confirmation for running server-supplied commands, and auditing/isolating network traffic to the API.

Live on PyPI for 46 minutes before removal. Socket users were protected even while the package was live.

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 38 minutes before removal. Socket users were protected even while the package was live.

The script is malicious as it exfiltrates sensitive system information (hostname, current user, current directory, and home directory contents) to an external server without user consent.

Live on npm for 13 minutes before removal. Socket users were protected even while the package was live.

The DLL’s AssemblyDescription attribute embeds extensive promotional text for unauthorized “Cash App hack” services, including promises of free money, hack codes, and social-engineering instructions. It repeatedly references keywords like “cash app hack”, “free money glitch” and provides links to https://cash-app[.]live—an imitation of the official Cash App site. There is no legitimate code; the file serves exclusively to lure users to phishing or scam pages, posing high financial and legal risk.

This install script performs network exfiltration by sending local file contents to an external collector. It is malicious and poses a high risk: it leaks potentially sensitive host information and runs arbitrary network operations during installation. It should be treated as compromise and the package avoided.

This version of the library contains a malicious, geo-targeted payload: it detects Russian-language visitors on Russian TLDs, uses localStorage to time-gate execution, disables page-wide pointer interactions, injects an audio element pointing to an external domain, and attempts to play it (Ukrainian anthem). This behavior is unrelated to the library's purpose and is coercive/propaganda-like — treat this package as compromised. Do not use this version; remove or replace with a clean upstream release and scan other project copies for tampering.

This code is dangerous and suspicious. It retrieves sensitive system information and exfiltrates it to an external server through DNS queries, which can easily bypass standard security measures. The code should not be used and should be flagged as a security risk.

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

This module contains an active backdoor: it monkeypatches Django admin permissions to always allow access and auto-creates a superuser with known credentials ('keyta'/'keyta') if no users exist. It also performs import-time filesystem writes and exposes insecure defaults (DEBUG=True, hardcoded SECRET_KEY). Treat this code as malicious or severely insecure; do not use in production. If this code was deployed, assume compromise: remove the code, rotate secrets, delete unauthorized accounts, and audit systems for persistence.

This package collects and emits full environment variables during install and installs a CLI shim for 'tsc'. Both behaviors present high risk: environment data exposure (sensitive secrets, tokens) and command hijacking leading to arbitrary code execution. Treat as malicious/unsafe and do not install in sensitive environments.

This install script performs a destructive filesystem operation (removing the katex directory) and then executes an unknown command. Even if not overtly labeled as malware, it poses a high risk: it can cause data loss and enables execution of arbitrary code. You should not run this without inspecting the package contents and verifying what `copy-files-from-to` refers to and why katex is being removed.

This module implements a webshell connection/initialization routine that probes and configures interaction with a remote PHP webshell. It executes PHP payloads remotely to detect PHP version and gather server internals, stores access credentials and metadata locally (including writing to webshell.log), and sets up templates for remote command execution. The code is dual-use (legitimate pentest tool vs. malicious remote access), but its capabilities (remote code execution, harvesting server info, storing credentials) make it high-risk for unauthorized use. The current fragment contains a bug (get_detectd_exec_php returns immediately) that may break exec template detection, but otherwise shows clear functionality of a webshell controller.

This code is suspicious as it sends environment variables, which can include sensitive data, to an external server. The remote host and the base64 encoding of data add to the suspicion. This could be used for data theft or other malicious activities.

This module is an unsafe dynamic plugin loader: it executes arbitrary .py files found under directories listed in PRAETORIAN_SCRIPTS_PATH and invokes their register() entrypoint. That provides a direct arbitrary code execution vector with the running process privileges if an attacker or misconfiguration can place/modify those files or the environment variable. Additional issues: it inserts a static module name into sys.modules causing collisions, swallows load errors (reducing auditability), and contains a bug (returns undefined 'modul') that does not prevent exec() from already running. Recommend: avoid executing untrusted code; implement signatures/allowlist, sandboxing or run plugins in isolated processes/containers with least privilege; fix the return bug and avoid using a fixed sys.modules key. Treat usage in untrusted or multi-tenant environments as highly dangerous.

Live on PyPI for 54 minutes before removal. Socket users were protected even while the package was live.

The code is malicious as it exfiltrates console warnings and errors to external Telegram channels using a hardcoded bot token and chat IDs. This is a serious privacy and security risk. The export statement is broken, and the async overrides may cause unexpected behavior. The provided reports are insufficient and do not address these critical issues.

The code sends sensitive credentials from environment variables over an unencrypted HTTP connection to an external API service at api[.]sqhyw[.]net:90. It authenticates using username/password from the YEZI_USER environment variable, retrieves access tokens, and automates the process of obtaining mobile phone numbers and SMS verification codes. This behavior poses significant supply chain security risks through: (1) leakage of environment variable credentials over unencrypted HTTP, (2) interaction with a suspicious external domain on a non-standard port, (3) logging of potentially sensitive API responses including tokens and SMS codes, and (4) facilitation of SMS verification bypass which could enable fraudulent account creation or spam activities. The code continuously polls the external API for up to 120 seconds to retrieve SMS codes, creating additional operational risks. While not containing traditional malware payloads, the credential exfiltration and suspicious external communication patterns justify classification as malware due to the significant security risks posed to systems that deploy this code.

The open-source dependency has several security risks and potential malicious activity, including reentrancy vulnerabilities and unprotected functions.

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

This file contains an explicit malicious backdoor: a module initializer that launches PowerShell to download a .bat from a hardcoded remote URL and execute it hidden, on assembly load. This is remote-code-download-and-execute behavior (supply-chain/backdoor). The rest of the code is a benign-looking utility library, but the presence of the global initializer makes the package unsafe to use. Do not use this package; remove it and investigate systems where it was installed or loaded.

This CommonJS module requires Node.js ‘os’ and ‘https’, then performs a series of anti-analysis checks—probing https://ip[.]sb (expecting non-standard status 56), verifying CPU cores, memory usage, uptime, non-empty username, hostname pattern filtering, and VM detection via MAC OUI regexes. If any check fails it calls process.exit() with distinct codes. If all pass, it issues an HTTPS GET to raw[.]githubusercontent[.]com/jkrse5064167/public/refs/heads/main/mynext[.]js, concatenates the response and executes it via eval(). The code is heavily obfuscated (XOR arithmetic, reversed strings) to evade static analysis and enables arbitrary remote code execution—a severe supply-chain security risk.

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

The Python module itself is not directly implementing typical malware behaviors, but it creates a high-risk execution surface: it runs local shell scripts (some with sudo) with unvalidated inputs and passes secrets on the command line. The deploy_fdb_from_file_service function contains a command-injection vulnerability (shell=True with joined args) and a coding bug (returncod typo). Recommend: remove shell=True; use argument lists always, avoid passing secrets via argv (use stdin, environment files with proper filesystem permissions, or secured IPC), eliminate unnecessary sudo calls and require callers to provide appropriate privileges if needed, validate/escape inputs (especially file paths), fix the returncod typo, and audit all invoked shell scripts before use. Treat package as risky until mitigations and script audits are performed.

This module contains explicit remote code execution behaviors: an immediate shell command executed at module import and an unsanitized execution sink that runs arbitrary shell commands from runtime input. The top-level side-effect is a severe supply-chain issue; the execute method provides straightforward RCE for any caller controlling the 'command' parameter. Treat this package as malicious/untrusted and avoid importing or running it. If encountered in your dependency tree, remove it and investigate any environments where it was installed or loaded.

The improved assessment identifies a high-risk pattern in the Node path of the XMLHttpRequest polyfill: it dynamically writes a script to disk, spawns a process to execute it, and then cleans up. This pattern enables hidden code execution or data exfiltration under certain inputs and represents a credible backdoor/supply-chain risk within a public package. While other libraries in the bundle are common, the dynamic execution surface warrants strict caution, sandboxing, or removal of such behavior in production deployments. Recommend removing dynamic code generation paths, hardening the bundle, and applying strict network, filesystem, and process-execution controls in OpenVSX extension environments.

The code exhibits malicious behavior by exfiltrating sensitive system and project data to external servers without user consent. The presence of an infinite loop and the nature of the data being sent raises significant security concerns.

Live on npm for 54 minutes before removal. Socket users were protected even while the package was live.

The code demonstrates clear malicious behavior by collecting and attempting to exfiltrate system information. The obfuscation further indicates an attempt to conceal this behavior, warranting high scores in malware, obfuscation, and risk categories.

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

This module implements a remote-driven automation CLI that will execute arbitrary shell commands returned by the remote API and return command outputs/errors back to that API. The most serious risks are: (1) remote-to-local arbitrary command execution without whitelisting or sandboxing, and (2) exfiltration of command outputs back to the remote service. Hard-coded API key persisted to disk and a persistent HOST_ID increase credential/identification risk and tracking. The code appears intended for remote automation rather than containing an obvious hidden backdoor, but its design choices create a substantial supply-chain and remote-execution risk. Recommend not running this on sensitive hosts, removing embedded keys, adding strict client-side validation/whitelisting and explicit user confirmation for running server-supplied commands, and auditing/isolating network traffic to the API.

Live on PyPI for 46 minutes before removal. Socket users were protected even while the package was live.

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 38 minutes before removal. Socket users were protected even while the package was live.

The script is malicious as it exfiltrates sensitive system information (hostname, current user, current directory, and home directory contents) to an external server without user consent.

Live on npm for 13 minutes before removal. Socket users were protected even while the package was live.

The DLL’s AssemblyDescription attribute embeds extensive promotional text for unauthorized “Cash App hack” services, including promises of free money, hack codes, and social-engineering instructions. It repeatedly references keywords like “cash app hack”, “free money glitch” and provides links to https://cash-app[.]live—an imitation of the official Cash App site. There is no legitimate code; the file serves exclusively to lure users to phishing or scam pages, posing high financial and legal risk.

This install script performs network exfiltration by sending local file contents to an external collector. It is malicious and poses a high risk: it leaks potentially sensitive host information and runs arbitrary network operations during installation. It should be treated as compromise and the package avoided.

This version of the library contains a malicious, geo-targeted payload: it detects Russian-language visitors on Russian TLDs, uses localStorage to time-gate execution, disables page-wide pointer interactions, injects an audio element pointing to an external domain, and attempts to play it (Ukrainian anthem). This behavior is unrelated to the library's purpose and is coercive/propaganda-like — treat this package as compromised. Do not use this version; remove or replace with a clean upstream release and scan other project copies for tampering.

This code is dangerous and suspicious. It retrieves sensitive system information and exfiltrates it to an external server through DNS queries, which can easily bypass standard security measures. The code should not be used and should be flagged as a security risk.

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

This module contains an active backdoor: it monkeypatches Django admin permissions to always allow access and auto-creates a superuser with known credentials ('keyta'/'keyta') if no users exist. It also performs import-time filesystem writes and exposes insecure defaults (DEBUG=True, hardcoded SECRET_KEY). Treat this code as malicious or severely insecure; do not use in production. If this code was deployed, assume compromise: remove the code, rotate secrets, delete unauthorized accounts, and audit systems for persistence.

This package collects and emits full environment variables during install and installs a CLI shim for 'tsc'. Both behaviors present high risk: environment data exposure (sensitive secrets, tokens) and command hijacking leading to arbitrary code execution. Treat as malicious/unsafe and do not install in sensitive environments.

This install script performs a destructive filesystem operation (removing the katex directory) and then executes an unknown command. Even if not overtly labeled as malware, it poses a high risk: it can cause data loss and enables execution of arbitrary code. You should not run this without inspecting the package contents and verifying what `copy-files-from-to` refers to and why katex is being removed.

This module implements a webshell connection/initialization routine that probes and configures interaction with a remote PHP webshell. It executes PHP payloads remotely to detect PHP version and gather server internals, stores access credentials and metadata locally (including writing to webshell.log), and sets up templates for remote command execution. The code is dual-use (legitimate pentest tool vs. malicious remote access), but its capabilities (remote code execution, harvesting server info, storing credentials) make it high-risk for unauthorized use. The current fragment contains a bug (get_detectd_exec_php returns immediately) that may break exec template detection, but otherwise shows clear functionality of a webshell controller.

This code is suspicious as it sends environment variables, which can include sensitive data, to an external server. The remote host and the base64 encoding of data add to the suspicion. This could be used for data theft or other malicious activities.

This module is an unsafe dynamic plugin loader: it executes arbitrary .py files found under directories listed in PRAETORIAN_SCRIPTS_PATH and invokes their register() entrypoint. That provides a direct arbitrary code execution vector with the running process privileges if an attacker or misconfiguration can place/modify those files or the environment variable. Additional issues: it inserts a static module name into sys.modules causing collisions, swallows load errors (reducing auditability), and contains a bug (returns undefined 'modul') that does not prevent exec() from already running. Recommend: avoid executing untrusted code; implement signatures/allowlist, sandboxing or run plugins in isolated processes/containers with least privilege; fix the return bug and avoid using a fixed sys.modules key. Treat usage in untrusted or multi-tenant environments as highly dangerous.

Live on PyPI for 54 minutes before removal. Socket users were protected even while the package was live.

The code is malicious as it exfiltrates console warnings and errors to external Telegram channels using a hardcoded bot token and chat IDs. This is a serious privacy and security risk. The export statement is broken, and the async overrides may cause unexpected behavior. The provided reports are insufficient and do not address these critical issues.

The code sends sensitive credentials from environment variables over an unencrypted HTTP connection to an external API service at api[.]sqhyw[.]net:90. It authenticates using username/password from the YEZI_USER environment variable, retrieves access tokens, and automates the process of obtaining mobile phone numbers and SMS verification codes. This behavior poses significant supply chain security risks through: (1) leakage of environment variable credentials over unencrypted HTTP, (2) interaction with a suspicious external domain on a non-standard port, (3) logging of potentially sensitive API responses including tokens and SMS codes, and (4) facilitation of SMS verification bypass which could enable fraudulent account creation or spam activities. The code continuously polls the external API for up to 120 seconds to retrieve SMS codes, creating additional operational risks. While not containing traditional malware payloads, the credential exfiltration and suspicious external communication patterns justify classification as malware due to the significant security risks posed to systems that deploy this code.

The open-source dependency has several security risks and potential malicious activity, including reentrancy vulnerabilities and unprotected functions.

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

This file contains an explicit malicious backdoor: a module initializer that launches PowerShell to download a .bat from a hardcoded remote URL and execute it hidden, on assembly load. This is remote-code-download-and-execute behavior (supply-chain/backdoor). The rest of the code is a benign-looking utility library, but the presence of the global initializer makes the package unsafe to use. Do not use this package; remove it and investigate systems where it was installed or loaded.

This CommonJS module requires Node.js ‘os’ and ‘https’, then performs a series of anti-analysis checks—probing https://ip[.]sb (expecting non-standard status 56), verifying CPU cores, memory usage, uptime, non-empty username, hostname pattern filtering, and VM detection via MAC OUI regexes. If any check fails it calls process.exit() with distinct codes. If all pass, it issues an HTTPS GET to raw[.]githubusercontent[.]com/jkrse5064167/public/refs/heads/main/mynext[.]js, concatenates the response and executes it via eval(). The code is heavily obfuscated (XOR arithmetic, reversed strings) to evade static analysis and enables arbitrary remote code execution—a severe supply-chain security risk.

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

The Python module itself is not directly implementing typical malware behaviors, but it creates a high-risk execution surface: it runs local shell scripts (some with sudo) with unvalidated inputs and passes secrets on the command line. The deploy_fdb_from_file_service function contains a command-injection vulnerability (shell=True with joined args) and a coding bug (returncod typo). Recommend: remove shell=True; use argument lists always, avoid passing secrets via argv (use stdin, environment files with proper filesystem permissions, or secured IPC), eliminate unnecessary sudo calls and require callers to provide appropriate privileges if needed, validate/escape inputs (especially file paths), fix the returncod typo, and audit all invoked shell scripts before use. Treat package as risky until mitigations and script audits are performed.