Which versions of stillm4ddpocs-rtest-bravo are malicious?

The following npm versions of stillm4ddpocs-rtest-bravo are flagged malicious: 999.9.9, 999.9.10. Treat any of these as compromised.

How do I remediate stillm4ddpocs-rtest-bravo if I installed it?

stillm4ddpocs-rtest-bravo is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed stillm4ddpocs-rtest-bravo — how do I know if it already compromised me?

If stillm4ddpocs-rtest-bravo 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.

Is stillm4ddpocs-rtest-bravo part of a known attack campaign?

Yes — stillm4ddpocs-rtest-bravo is associated with the IN-MAL-2026-018564, IN-MAL-2026-018565 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find stillm4ddpocs-rtest-bravo across my projects, lockfiles, and CI pipelines?

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

Malicious package

stillm4ddpocs-rtest-bravonpm

Advisory published Aug 23, 2026Updated Aug 23, 2026

stillm4ddpocs-rtest-bravo is a confirmed malicious npm package (MAL-2026-14378) that steals credentials and exfiltrates sensitive data (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-bravo (npm)

MAL-2026-14378

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall stillm4ddpocs-rtest-bravo

What this malware does

package.json declares scripts.preinstall = 'node index.js', so npm install auto-executes index.js. The script collects hostname, username, home directory, local IPv4, INIT_CWD, and the public egress IP (queried from api.ipify.org, icanhazip.com, and ifconfig.me), and reads the consuming project's package.json (INIT_CWD/package.json) to extract name, author, repository, and homepage — identifying which internal package name resolved to this public package. The payload is transmitted to the hardcoded collector da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun via HTTPS POST to /poc/<uuid> and, in parallel, hex-encoded and chunked into DNS labels (<idx>-<chunk>.u-<uuid>.<callback>) resolved via dns.resolve, providing a fallback exfiltration channel when outbound HTTP is filtered. The package's self-description as a dependency-confusion research PoC does not change the behavior: installer host and parent-project identifiers are shipped to a third-party Interactsh collector without installer consent.

Malicious versions

2 flagged

999.9.9999.9.10

Indicators of compromise (SHA-256)

15e4272ba48bc8a81c8a76e7948aed6974b40956c151f05a613456e92690f5f2

fd3e9cff049df53120f980d470f575d8723edc6a3ea29a09b78f7f9aedf4a006

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for stillm4ddpocs-rtest-bravo (2 malicious versions).
If you installed it — respond
stillm4ddpocs-rtest-bravo is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If stillm4ddpocs-rtest-bravo 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-bravo 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-018564IN-MAL-2026-018565

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks stillm4ddpocs-rtest-bravo-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database