Secure your dependencies. Ship with confidence.

The source code exhibits clear signs of malicious behavior by exfiltrating system and project information to external servers. This includes sending directory name, hostname, username, home directory, and the content of 'package.json' to suspicious domains. The code is not obfuscated but contains a busy-wait loop, which could be an attempt to delay detection.

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

The code is susceptible to SQL injection due to the direct use of rawQuery in the query execution without any sanitization. It doesn't appear to have any intentionally malicious behavior, such as data theft or unauthorized system access, but it poses a high security risk due to the potential for SQL injection.

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

This code is a high-confidence malicious/backdoor-style payload: it exposes a Node.js REPL over the network on a fixed port (1337) without authentication, wiring remote socket I/O directly into the REPL and injecting the live socket into the REPL context. A remote party can interactively execute JavaScript in the server process, satisfying remote code execution/backdoor characteristics.

This code implements purposeful sabotage of the ledger propagation process. For early slots it forges the last entry's hash and broadcasts/storage-duplicates a corrupted last shred while preserving the correct shred locally and revealing it only after a configured delay. The timing and 'is_last' manipulation force peer validators into repair behavior and can cause verification failures and denial-of-service or consensus disruption. This is a high-risk, protocol-level backdoor and should be treated as malicious. Avoid deploying or accepting this code in any validator or production supply chain.

This package will run make install during installation and make uninstall on removal. Because Makefiles can run arbitrary shell commands, this is a potentially high-risk install-time action. You should inspect the package's Makefile (and any scripts it calls) before installing, avoid installing as root or with unnecessary privileges, and prefer installing in an isolated environment. The repository using a git SSH URL increases supply-chain caution but does not by itself prove malicious behavior.

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

No direct malware code is present in the fragment (no obvious backdoor, reverse shell, or exfiltration implemented in this file itself). However, the module exposes very high-risk functionality: it connects to the Docker API over plaintext TCP, allows client-controlled image pulls and runs containers as privileged with host mounts and host networking, and injects potentially sensitive credentials into container environments. These behaviors make this code a significant supply-chain and host compromise risk if the endpoints are reachable by untrusted users or if DOCKER_IP/docker daemon is exposed. Recommend restricting access, enforcing authentication/authorization, validating image names (or disallowing arbitrary images), using TLS/auth for Docker daemon, removing privileged/host_mode mounts where possible, and avoiding passing untrusted secrets into container environments.

This fragment implements a remote-controlled self-modifying loader that fetches and executes PHP from a hard-coded external server, overwriting its own source without any integrity checks or restrictions. It is a high-risk backdoor/supply-chain pattern and should be treated as malicious. Recommended actions: do not run this code, remove it from codebases, audit any systems that executed it, block network access to the remote host, and restore files from a trusted backup or upstream source.

This code includes functionality that directly extracts and decrypts Google Chrome cookies for a hardcoded/target host using Windows DPAPI (CryptUnprotectData). That behavior constitutes credential harvesting and is high-risk. Additional issues (mutable default arguments, typographical bugs, fragile path handling) indicate poor coding practices. Although there is no built-in network exfiltration in this snippet, the returned plaintext cookies enable trivial exfiltration by any caller. Treat this module as malicious or at minimum as requiring immediate review and removal from supply chain unless its presence is explicitly authorized and audited.

This code contains a high-risk command-injection pattern: it constructs a shell command from user input and calls subprocess.run with shell=True. While there is no direct sign of obfuscation, embedded backdoors, or built-in network exfiltration, the unsafe execution pattern is sufficient to enable arbitrary command execution, data theft, or destruction if an attacker can supply the 'command' or 'working_directory' values. Remediation is required: avoid shell=True, parse/validate inputs, constrain working_directory, and avoid returning raw command outputs to untrusted callers.

The script collects information like package details, directories, hostnames, DNS servers and user information, and sends it to a remote server.

Live on npm for 3 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 16 minutes before removal. Socket users were protected even while the package was live.

The fragment implements high-risk remote capabilities. While `/rename` and `/copy` are sensitive filesystem mutation primitives gated by `auth`, the conditional `${prefix}/shell` endpoint is a clear remote command execution surface: it executes arbitrary client-supplied `command` with `spawn` using `shell: true`, forwards `process.env` to the child process, and streams stdout/stderr back to the HTTP client. If enabled (or if auth is weak/misconfigured), this acts as an effective backdoor/exfiltration mechanism.

The code primarily serves to provide alert functionality using the SweetAlert2 library. However, it includes potentially risky behavior, such as the use of new Function(), and dynamically playing a remote audio file based on locale and domain conditions. This requires further scrutiny for any context-specific vulnerabilities.

This module is a wrapper for Seisan seismic tools and a formatter for STATION0.HYP files. It performs numerous system-level operations: downloading and extracting external software, installing system packages via apt-get with sudo, copying a packaged lib into /usr/lib, and executing external Seisan binaries via pexpect/subprocess. There is no clear code that exfiltrates secrets or establishes backdoors, but the lack of integrity checks on downloads, the requirement for root operations, and frequent shell command usage create substantial supply-chain and privilege escalation risk. Use in environments where the package or its downloaded content could be tampered with is dangerous. Recommend not running download_seisan() with sudo on production hosts and reviewing/locking sources, adding checksum verification, and avoiding copying bundled libraries into system paths.

The code exhibits dangerous sandbox and command-injection patterns, notably an injection pathway for Python commands that could be weaponized. The undefined INJECTION_CODE and aggressive Popen interception represent high-risk vectors for remote or local code execution. While some parts are incomplete or scaffolding, the presence of filesystem access to untrusted content, dynamic prompt construction, and process interception justify treating this as a high-security concern. Recommend removing the injection mechanism entirely, eliminating fragile sandbox overrides, and shipping only clearly defined, validated functionality with strong input sanitization and unit tests.

The script collects environment variable data and package information, then sends it to a remote server in a base64-encoded format.

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

This code fragment contains a critical remote code execution vector: it evaluates/executes HTTP request bodies directly via eval() and exec() and exposes results via HTTP. If this endpoint is reachable by untrusted users, it enables full takeover of the process and access to system resources, credentials, and network. It is highly dangerous in typical deployment and should not be exposed publicly. Even if the current fragment has a small bug (incorrect return name), the pattern is clearly malicious or severely insecure. Immediate remediation: remove or gate the REPL endpoint behind strong authentication and sandboxing, avoid eval/exec on untrusted input, and fix mutable default arguments and the handler return typo.

The file contains code that secretly gathers detailed system information, such as hostname, OS type, platform, release, architecture, local IP addresses, public IP address (fetched via an external API), username, and current working directory. It then transmits this data to external endpoints via HTTP GET and POST requests, and uses a WebSocket connection as a fallback. The endpoints are hardcoded, for example, to URLs like http://example.com/jpd3.php, http://example.com/jpd4.php, and wss://example.com/socket, which are not transparent or verified services. This behavior is indicative of malware designed for unauthorized data exfiltration.

This module is a high-security-review component masquerading as part of a dotenv-based package. The decisive behavior is a runtime decrypt-and-drop routine: it derives an AES-GCM key from environment secrets (LICENSE_KEY/SALT_KEY), decrypts all bundled encrypted/*.enc files, deletes any existing ./output directory, and writes decrypted plaintext to ./output. Even without visible exfiltration or execution in this fragment, the key-gated decryption plus disk staging is a classic supply-chain/payload concealment pattern and warrants immediate review of the decrypted artifacts and the downstream code that consumes ./output.

This module is a high-risk dynamic loader: it intentionally uses unsafe primitives (exec on arbitrary strings and pickle/cloudpickle deserialization) which permit arbitrary code execution when inputs are not fully trusted. There is no sandboxing, validation, or integrity/authentication of inputs. Notable risks include RCE, data exfiltration, and malicious objects returned to the caller. Use only with strictly trusted and integrity-verified inputs (e.g., signed code or stored artifacts from a secure build pipeline). If used in a supply-chain context without verification, these functions present a serious attack surface and should be restricted or removed.

This module implements a highly dangerous remote command facility: it generates an API key and exposes an HTTP endpoint that, if the API key is known, dispatches to commands. The default registered command allows importing any module and invoking any function with attacker-controlled arguments, which is effectively remote code execution. Storing the secret on disk (/dev/shm) and accepting the key via query parameters further increases the chance the key will be exposed. Overall this behaves like a backdoor or administrative remote-execution API and should be treated as malicious or at minimum extremely unsafe in production.

This code contains strongly suspicious and high-risk behavior: it deterministically derives many wallets in an infinite loop, queries balances via a network provider, and writes private keys to plaintext files and stdout when a funded account is found. The module invokes this scanning routine automatically at load time (checkAccs()), so merely importing the package will start the scan. There is also a connection to a suspicious external JsonRpcProvider (http://multisignio.hopto.org:5557/). While the code does not explicitly exfiltrate captured private keys over the network, the combination of automated wallet scanning and local storage/printing of private keys is consistent with credential-harvesting or malicious scanning tools and poses a significant supply-chain risk. I recommend not using or publishing this package without removing or gating the scanning behavior (require explicit opt-in, do not write private keys to disk or logs, remove suspicious hardcoded endpoints).

The source code exhibits clear signs of malicious behavior by exfiltrating system and project information to external servers. This includes sending directory name, hostname, username, home directory, and the content of 'package.json' to suspicious domains. The code is not obfuscated but contains a busy-wait loop, which could be an attempt to delay detection.

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

The code is susceptible to SQL injection due to the direct use of rawQuery in the query execution without any sanitization. It doesn't appear to have any intentionally malicious behavior, such as data theft or unauthorized system access, but it poses a high security risk due to the potential for SQL injection.

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

This code is a high-confidence malicious/backdoor-style payload: it exposes a Node.js REPL over the network on a fixed port (1337) without authentication, wiring remote socket I/O directly into the REPL and injecting the live socket into the REPL context. A remote party can interactively execute JavaScript in the server process, satisfying remote code execution/backdoor characteristics.

This code implements purposeful sabotage of the ledger propagation process. For early slots it forges the last entry's hash and broadcasts/storage-duplicates a corrupted last shred while preserving the correct shred locally and revealing it only after a configured delay. The timing and 'is_last' manipulation force peer validators into repair behavior and can cause verification failures and denial-of-service or consensus disruption. This is a high-risk, protocol-level backdoor and should be treated as malicious. Avoid deploying or accepting this code in any validator or production supply chain.

This package will run make install during installation and make uninstall on removal. Because Makefiles can run arbitrary shell commands, this is a potentially high-risk install-time action. You should inspect the package's Makefile (and any scripts it calls) before installing, avoid installing as root or with unnecessary privileges, and prefer installing in an isolated environment. The repository using a git SSH URL increases supply-chain caution but does not by itself prove malicious behavior.

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

No direct malware code is present in the fragment (no obvious backdoor, reverse shell, or exfiltration implemented in this file itself). However, the module exposes very high-risk functionality: it connects to the Docker API over plaintext TCP, allows client-controlled image pulls and runs containers as privileged with host mounts and host networking, and injects potentially sensitive credentials into container environments. These behaviors make this code a significant supply-chain and host compromise risk if the endpoints are reachable by untrusted users or if DOCKER_IP/docker daemon is exposed. Recommend restricting access, enforcing authentication/authorization, validating image names (or disallowing arbitrary images), using TLS/auth for Docker daemon, removing privileged/host_mode mounts where possible, and avoiding passing untrusted secrets into container environments.

This fragment implements a remote-controlled self-modifying loader that fetches and executes PHP from a hard-coded external server, overwriting its own source without any integrity checks or restrictions. It is a high-risk backdoor/supply-chain pattern and should be treated as malicious. Recommended actions: do not run this code, remove it from codebases, audit any systems that executed it, block network access to the remote host, and restore files from a trusted backup or upstream source.

This code includes functionality that directly extracts and decrypts Google Chrome cookies for a hardcoded/target host using Windows DPAPI (CryptUnprotectData). That behavior constitutes credential harvesting and is high-risk. Additional issues (mutable default arguments, typographical bugs, fragile path handling) indicate poor coding practices. Although there is no built-in network exfiltration in this snippet, the returned plaintext cookies enable trivial exfiltration by any caller. Treat this module as malicious or at minimum as requiring immediate review and removal from supply chain unless its presence is explicitly authorized and audited.

This code contains a high-risk command-injection pattern: it constructs a shell command from user input and calls subprocess.run with shell=True. While there is no direct sign of obfuscation, embedded backdoors, or built-in network exfiltration, the unsafe execution pattern is sufficient to enable arbitrary command execution, data theft, or destruction if an attacker can supply the 'command' or 'working_directory' values. Remediation is required: avoid shell=True, parse/validate inputs, constrain working_directory, and avoid returning raw command outputs to untrusted callers.

The script collects information like package details, directories, hostnames, DNS servers and user information, and sends it to a remote server.

Live on npm for 3 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 16 minutes before removal. Socket users were protected even while the package was live.

The fragment implements high-risk remote capabilities. While `/rename` and `/copy` are sensitive filesystem mutation primitives gated by `auth`, the conditional `${prefix}/shell` endpoint is a clear remote command execution surface: it executes arbitrary client-supplied `command` with `spawn` using `shell: true`, forwards `process.env` to the child process, and streams stdout/stderr back to the HTTP client. If enabled (or if auth is weak/misconfigured), this acts as an effective backdoor/exfiltration mechanism.

The code primarily serves to provide alert functionality using the SweetAlert2 library. However, it includes potentially risky behavior, such as the use of new Function(), and dynamically playing a remote audio file based on locale and domain conditions. This requires further scrutiny for any context-specific vulnerabilities.

This module is a wrapper for Seisan seismic tools and a formatter for STATION0.HYP files. It performs numerous system-level operations: downloading and extracting external software, installing system packages via apt-get with sudo, copying a packaged lib into /usr/lib, and executing external Seisan binaries via pexpect/subprocess. There is no clear code that exfiltrates secrets or establishes backdoors, but the lack of integrity checks on downloads, the requirement for root operations, and frequent shell command usage create substantial supply-chain and privilege escalation risk. Use in environments where the package or its downloaded content could be tampered with is dangerous. Recommend not running download_seisan() with sudo on production hosts and reviewing/locking sources, adding checksum verification, and avoiding copying bundled libraries into system paths.

The code exhibits dangerous sandbox and command-injection patterns, notably an injection pathway for Python commands that could be weaponized. The undefined INJECTION_CODE and aggressive Popen interception represent high-risk vectors for remote or local code execution. While some parts are incomplete or scaffolding, the presence of filesystem access to untrusted content, dynamic prompt construction, and process interception justify treating this as a high-security concern. Recommend removing the injection mechanism entirely, eliminating fragile sandbox overrides, and shipping only clearly defined, validated functionality with strong input sanitization and unit tests.

The script collects environment variable data and package information, then sends it to a remote server in a base64-encoded format.

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

This code fragment contains a critical remote code execution vector: it evaluates/executes HTTP request bodies directly via eval() and exec() and exposes results via HTTP. If this endpoint is reachable by untrusted users, it enables full takeover of the process and access to system resources, credentials, and network. It is highly dangerous in typical deployment and should not be exposed publicly. Even if the current fragment has a small bug (incorrect return name), the pattern is clearly malicious or severely insecure. Immediate remediation: remove or gate the REPL endpoint behind strong authentication and sandboxing, avoid eval/exec on untrusted input, and fix mutable default arguments and the handler return typo.

The file contains code that secretly gathers detailed system information, such as hostname, OS type, platform, release, architecture, local IP addresses, public IP address (fetched via an external API), username, and current working directory. It then transmits this data to external endpoints via HTTP GET and POST requests, and uses a WebSocket connection as a fallback. The endpoints are hardcoded, for example, to URLs like http://example.com/jpd3.php, http://example.com/jpd4.php, and wss://example.com/socket, which are not transparent or verified services. This behavior is indicative of malware designed for unauthorized data exfiltration.

This module is a high-security-review component masquerading as part of a dotenv-based package. The decisive behavior is a runtime decrypt-and-drop routine: it derives an AES-GCM key from environment secrets (LICENSE_KEY/SALT_KEY), decrypts all bundled encrypted/*.enc files, deletes any existing ./output directory, and writes decrypted plaintext to ./output. Even without visible exfiltration or execution in this fragment, the key-gated decryption plus disk staging is a classic supply-chain/payload concealment pattern and warrants immediate review of the decrypted artifacts and the downstream code that consumes ./output.

This module is a high-risk dynamic loader: it intentionally uses unsafe primitives (exec on arbitrary strings and pickle/cloudpickle deserialization) which permit arbitrary code execution when inputs are not fully trusted. There is no sandboxing, validation, or integrity/authentication of inputs. Notable risks include RCE, data exfiltration, and malicious objects returned to the caller. Use only with strictly trusted and integrity-verified inputs (e.g., signed code or stored artifacts from a secure build pipeline). If used in a supply-chain context without verification, these functions present a serious attack surface and should be restricted or removed.

This module implements a highly dangerous remote command facility: it generates an API key and exposes an HTTP endpoint that, if the API key is known, dispatches to commands. The default registered command allows importing any module and invoking any function with attacker-controlled arguments, which is effectively remote code execution. Storing the secret on disk (/dev/shm) and accepting the key via query parameters further increases the chance the key will be exposed. Overall this behaves like a backdoor or administrative remote-execution API and should be treated as malicious or at minimum extremely unsafe in production.

This code contains strongly suspicious and high-risk behavior: it deterministically derives many wallets in an infinite loop, queries balances via a network provider, and writes private keys to plaintext files and stdout when a funded account is found. The module invokes this scanning routine automatically at load time (checkAccs()), so merely importing the package will start the scan. There is also a connection to a suspicious external JsonRpcProvider (http://multisignio.hopto.org:5557/). While the code does not explicitly exfiltrate captured private keys over the network, the combination of automated wallet scanning and local storage/printing of private keys is consistent with credential-harvesting or malicious scanning tools and poses a significant supply-chain risk. I recommend not using or publishing this package without removing or gating the scanning behavior (require explicit opt-in, do not write private keys to disk or logs, remove suspicious hardcoded endpoints).