Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

stillm4ddpocs-rtest-alphanpm

Advisory published Updated

stillm4ddpocs-rtest-alpha is a confirmed malicious npm package (MAL-2026-14377) that executes malicious code on install (malicious versions 999.9.9, 999.9.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stillm4ddpocs-rtest-alpha (npm)

MAL-2026-14377
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall stillm4ddpocs-rtest-alpha

What this malware does

package.json declares a preinstall hook that runs index.js on npm install. index.js collects the installer's local IPv4, public IP (via https://api.ipify.org, https://icanhazip.com, https://ifconfig.me), DNS-resolver IP, hostname, OS username, home directory, cwd, and the parent project's package.json name/author/repository/homepage, then transmits the JSON to the hardcoded callback da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun via three channels: HTTP POST on:80, HTTPS POST on:443, and DNS TXT queries whose labels carry the hex-encoded payload split into 60-character chunks. The DNS covert channel and hex chunking are structured to bypass egress filtering that blocks outbound HTTP. The package's self-description as 'authorised security research' does not gate execution; any project that resolves this name at install time transmits the data without consent. The 999.9.9 version and lure name are consistent with a dependency-confusion probe.

Malicious versions

2 flagged
999.9.9999.9.10

Indicators of compromise (SHA-256)

1838ad5b8199e05fbd2be46a4eeba578cbe40cf798b243fbc378e4ec4a84a8d9
47545f800dcb07213863afb8beab283755fb596ea7d5d478b60e4ff449453839

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for stillm4ddpocs-rtest-alpha (2 malicious versions).

  2. If you installed it — respond

    Remove stillm4ddpocs-rtest-alpha from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If stillm4ddpocs-rtest-alpha was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. stillm4ddpocs-rtest-alpha on npm has been identified as a malicious package (versions 999.9.9, 999.9.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018559IN-MAL-2026-018561

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks stillm4ddpocs-rtest-alpha-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

stillm4ddpocs-rtest-alpha (npm) malicious package — MAL-2026-14377 | O3 Security