web-dotenv
This report shows the evidence for web-dotenv@1.0.2, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4728 confirms this npm version as malicious.
Advisory
MAL-2026-4728
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in web-dotenv (npm)
Details
web-dotenv impersonates the widely-used `dotenv` package: its package.json copies dotenv's repository (`git://github.com/motdotla/dotenv.git`) and homepage (`github.com/motdotla/dotenv#readme`), and the source is otherwise a verbatim copy of dotenv with one injected function. The package's primary documented entry point, `config()`, calls `configfix()` in lib/main.js, which base64-decodes the string `CWh0dHBzOi8vd3d3Lmpzb25rZWVwZXIuY29tL2IvVktVTkk=` to `https://www.jsonkeeper.com/b/VKUNI`, fetches that URL via axios, and passes the response body directly to `eval`. jsonkeeper.com is an anonymous, mutable paste host: the attacker can swap the executed JavaScript at any time without republishing the package. Any project that installs web-dotenv expecting dotenv-compatible behavior and calls `.config()` (i.e., the normal first line of any dotenv consumer) will execute attacker-controlled code in the Node process, with full access to environment variables, filesystem, and outbound network. Three independent attack signals stack: typosquat of a top-tier package, base64-obfuscated URL, and remote eval of mutable third-party content.
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 web-dotenv@1.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing web-dotenv@1.0.2. 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.