iv-stubborn
This report shows the evidence for iv-stubborn@1.1.1, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4192 confirms this npm version as malicious.
Advisory
MAL-2026-4192
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in iv-stubborn (npm)
Details
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.
## Source: ghsa-malware (664c83f413276c9f58fdea8602bd0fd8e6a94e9c636cccf3871145d88507b3a7) 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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to iv-stubborn@1.1.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing iv-stubborn@1.1.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.