Malicious code in stillm4ddpocs-rtest-alpha (npm)
The npm package stillm4ddpocs-rtest-alpha (version 999.9.9) contained malicious code that executed a preinstall hook to exfiltrate system and project metadata without user consent. The package used multiple covert channels (HTTP, HTTPS, and DNS TXT queries) to transmit collected data to a hardcoded callback domain, with DNS encoding designed to bypass egress filtering.
- Disclosed
- Last updated
- Blast radius
- Any project that installs stillm4ddpocs-rtest-alpha via npm; data exfiltration affects all systems where the package is installed.
- Ecosystems
- Attack vectors
- Affected entities
- stillm4ddpocs-rtest-alpha · 999.9.9
The npm package stillm4ddpocs-rtest-alpha version 999.9.9 was published with a preinstall hook that automatically executed on installation. The hook collected sensitive system information including the installer's local and public IPv4 addresses, DNS resolver IP, hostname, OS username, home directory, current working directory, and metadata from the parent project's package.json (name, author, repository, homepage).\n\nThe collected data was transmitted to a hardcoded callback domain (da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun) via three separate channels: HTTP POST on port 80, HTTPS POST on port 443, and DNS TXT queries with hex-encoded payloads split into 60-character chunks. The use of DNS as a covert channel was specifically designed to bypass egress filtering that blocks outbound HTTP traffic.\n\nThe package's self-description claimed it was for "authorised security research," but this disclaimer did not prevent execution; any project resolving the package name at install time would transmit data without explicit user consent. The version number (999.9.9) and package name are consistent with a dependency-confusion attack probe.\n\nThe incident was identified and credited to the OpenSSF's malicious-packages repository (MAL-2026-14377).
Indicators of compromise
- Packages
- stillm4ddpocs-rtest-alpha
- Domains
- da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun
Remediation
- Remove stillm4ddpocs-rtest-alpha from all project dependencies immediately
- Audit npm install logs and lock files to identify if the package was ever installed in your environment
- Assume any system that installed this package has had system metadata and project information exfiltrated; review access logs and consider credential rotation if sensitive operations were performed
- Implement npm package allow-listing or use private registries to prevent dependency-confusion attacks
- Monitor outbound DNS and HTTP traffic for connections to da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun and related domains
- Use npm audit and supply-chain security tools to detect similar malicious packages
Sources
- GitHub Advisory GHSA-mrj6-mc6j-fpcm · GitHub Advisory Database
Cite this entry
"Malicious code in stillm4ddpocs-rtest-alpha (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 23, 2026; last updated August 23, 2026. https://supplychainattack.org/incident/malicious-code-in-stillm4ddpocs-rtest-alpha-npm-1eu6a4
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in lumen-pages-community (npm)
lumen-pages-community@9.9.9 on npm contains malicious code that executes a postinstall hook to exfiltrate installer metadata (hostname, username, working directory, platform, Node version, CI environment, npm user-agent) to a hardcoded webhook.site URL. The high version number and lack of functionality suggest a dependency-confusion attack.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in @gfe/lx-watcher (npm)
The npm package @gfe/lx-watcher contained malicious code that exfiltrated host metadata (hostname, OS username, working directory, timestamp) via npm lifecycle hooks to a hardcoded webhook.site endpoint. The package exploited dependency confusion by using a scoped name (@gfe/*) with a no-op stub, allowing silent resolution against the public registry while leaking host identifiers.
npmDependency confusionCompromised package