iv-stubbornnpm
Advisory published Updated
iv-stubborn is a confirmed malicious npm package (MAL-2026-4192) that steals credentials and exfiltrates sensitive data (malicious version 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in iv-stubborn (npm)
What this malware does
On npm install, both preinstall and postinstall lifecycle hooks execute index.js, which collects the installer's hostname, all non-internal network interface IP addresses, current working directory, and a specific environment variable (SECURITY_BUG_BOUNTY_DOCTOLIB_IS_PWN), and POSTs them as JSON over plain HTTP to http://poc.khz.bar/install. The README (# @doctolib-apps/native-personalized-services — Claimed by dphoeniixx) indicates this package was published as a dependency-confusion claim against an internal scope. Regardless of stated bug-bounty intent, any developer or build system that installs iv-stubborn automatically transmits internal-network identifiers to a third-party server without consent. The combination of namespace-confusion targeting plus install-time beaconing of host data over plaintext HTTP is a supply-chain attack pattern.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for iv-stubborn (version 1.1.1).
If you installed it — respond
iv-stubborn 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 iv-stubborn 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks iv-stubborn-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.