The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that executes during installation. It collects sensitive host and project metadata, including hostname, username, directory paths, IP addresses, DNS resolver info, and package.json fields, then exfiltrates this data to a hardcoded external server using HTTPS, HTTP, and covert DNS channels designed to bypass egress filtering. The package uses a high version number to facilitate a dependency confusion attack, causing npm to resolve the public malicious package over internal versions without user consent.
The npm package stillm4ddpocs-rtest-alpha versions 999.9.9 and 999.9.10 contains malicious code executed during installation. This code collects sensitive local environment information including IP addresses, hostname, OS username, and project metadata, then exfiltrates this data via HTTP, HTTPS, and DNS covert channels to a hardcoded callback domain. The package falsely claims to be authorized security research but transmits data without user consent. This behavior is consistent with dependency confusion attack probes.
The mcq-session npm package versions 1.0.3 and 1.0.4 contain malicious code that executes a hidden payload. When imported, the package runs an asynchronous function that reads an external file outside the package directory, decrypts it using a hardcoded DES key, and executes the decrypted JavaScript code via a detached Node.js subprocess. This behavior bypasses static code inspection by encrypting the payload and disguising the loader with misleading identifiers. The payload file is attacker-controlled and resides alongside the host application, enabling remote code execution without user consent or verification.
The npm package 'localize-translate' version 1.0.0 contains malicious code that executes during installation. Its postinstall script collects host identifiers such as hostname, platform, architecture, Node.js version, package name, timestamp, and npm lifecycle event, then sends this data as JSON to a hardcoded third-party server without user consent. This behavior constitutes an undisclosed, unconditional reconnaissance callback rather than legitimate telemetry.
The npm package karma-proxy version 1.0.0 contains malicious code that executes during installation. Its postinstall script collects host identifiers such as hostname, platform, architecture, Node.js version, package name, and lifecycle event, then sends this data as JSON to a hardcoded third-party endpoint unrelated to npm or the package vendor. This data collection occurs without user consent or disclosure.
The npm package localize-extract version 1.0.0 contains malicious code that executes a postinstall script. This script collects host identifiers such as hostname, platform, architecture, Node.js version, package name, and lifecycle event, then sends this data as JSON to a hardcoded external endpoint without user consent. The package appears to be a typosquatting attempt targeting the legitimate @angular/localize package, potentially as part of a dependency confusion attack.
The npm package named 'ngsw-config' version 1.0.0 contains malicious code that executes during the postinstall lifecycle script. This script collects host identifiers such as hostname, platform, architecture, Node version, package name, lifecycle name, and timestamp, then sends this data without user consent to a hardcoded external endpoint. The package name mimics Angular's legitimate tooling, likely to exploit dependency confusion in internal build systems, causing them to inadvertently leak identifying metadata.
The dxrs-dos npm package is a malicious toolkit advertised for DDoS attacks and botnet control. Upon loading, it executes code from an unpinned, author-controlled dependency, allowing arbitrary code execution. It also extracts a password-protected archive containing a PHP C2 panel into the working directory without user consent. The actual attack payloads activate only when explicitly invoked by the operator. This behavior enables the package author to run arbitrary code and drop opaque payloads on any system that installs or requires this package.
The npm package 'gaarf-node' version 1.0.0 contains malicious code that executes during installation. Its postinstall script collects host system identifiers and sends them without user consent to a hardcoded remote server unrelated to the impersonated legitimate project. This behavior occurs automatically as a side effect of installing the package.
The npm package gaarf-bq version 1.0.0 contains malicious code that executes during installation. Its postinstall script collects host identifiers such as hostname, platform, architecture, Node.js version, and package metadata, then sends this data to a hardcoded external server without user consent. This behavior is unrelated to the package's documented functionality and resembles dependency confusion tactics. No official patch or remediation guidance is provided.
The npm package code-assist-mcp version 1.0.0 contains malicious code that executes a postinstall script to collect host system identifiers and sends them to a hardcoded external server without user consent. This behavior occurs automatically during npm install and appears to be a reconnaissance beacon potentially used for dependency confusion or typosquatting attacks.
The npm package chromecast-webdriver-cli@1.0.0 contains malicious code that executes a postinstall script. This script collects host metadata such as hostname, platform, architecture, node version, package name, and npm lifecycle event, then sends this data to a third-party server without user consent. The package is a typosquat or dependency confusion attempt, mimicking a legitimate upstream tool but with no functional code beyond the data beacon.
The npm package 'broadcast-graphics-mcp' version 1.0.0 contains malicious code in its postinstall script that automatically executes upon installation. This script collects host identifiers such as hostname, platform, architecture, Node.js version, package name, npm lifecycle event, and timestamp, then sends this data as JSON to a hardcoded external server controlled by the package author. This behavior results in the exfiltration of installer machine metadata without user consent or configuration options.
The npm package streak-cal-core version 1.0.0 contains malicious code that drops and executes a large base64-encoded ELF binary upon import. The package disguises this payload within the main module file and executes it as a side effect, which is inconsistent with its advertised functionality as a calendar/streak helper. This behavior indicates the package is a typosquat variant designed to execute opaque native code without user consent.
The npm package 'chameleon-src' version 6.6.29 executes a preinstall script that collects and uploads the installer's public IP address and hostname to a hardcoded Sentry project without user consent or disclosure. This telemetry collection occurs during every npm install via a forced exception capture that sends data including personally identifiable information (PII) to the attacker's Sentry endpoint. The package name and description do not reveal this behavior, making it a covert data exfiltration risk.
The npm package axois-http is a typosquatting malicious package impersonating the legitimate axios library. It exports an empty object and contains a post-install script that collects platform information and sends it to a hardcoded IP address. On Windows or WSL environments, it downloads and executes a hidden native binary without user consent. The package has no legitimate functionality and is designed to stealthily execute malicious code during installation.
CodeWhale versions before 0.8.64 fail to properly validate the allow_shell configuration parameter from project config files, allowing attackers to enable arbitrary shell command execution by committing a malicious .codewhale/config.toml file to a repository. When a user clones and opens the repository in CodeWhale, the AI model gains access to exec_shell and task_shell tools, enabling execution of arbitrary shell commands on the victim's machine without explicit user consent.
The npm package bcc-design-icons version 9999.0.0 contains malicious code that executes a postinstall script during installation. This script sends the host's identifying information, including the hostname, to an attacker-controlled IP address without user consent. The package appears to be part of a dependency confusion attack, as it lacks expected functionality and uses a suspicious version number.
Attackers are exploiting Steam forums by posting malicious PowerShell commands disguised as troubleshooting advice. The command downloads and executes a script that installs a crypto miner (XMRig) on victims' Windows machines. The script mimics a system optimization tool to deceive users and disables antivirus scanning on the miner's folder. The miner hijacks system resources to mine Monero cryptocurrency without user consent, degrading performance and hardware lifespan. The attack relies on social engineering to trick gamers into running the harmful command with administrator privileges.
The kb-ai package on PyPI contains malicious code that, upon import, starts a background thread to collect system identifiers and sends them to a hardcoded Azure endpoint without user consent. This behavior is described in the package comments as a supply-chain proof-of-concept demonstrating a dependency confusion attack. The package also overrides the install command to execute malicious code during installation. The affected versions are 0.1.0 and 0.1.1.