Which versions of envparse2 are malicious?

The following npm versions of envparse2 are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate envparse2 if I installed it?

Remove envparse2 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.

I already installed envparse2 — how do I know if it already compromised me?

If envparse2 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is envparse2 part of a known attack campaign?

Yes — envparse2 is associated with the GHSA-q747-c2cv-gfhj, IN-MAL-2026-020300 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 envparse2 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for envparse2 (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging envparse2 across your stack and pipelines.

Malicious package

envparse2npm

envparse2 is a confirmed malicious npm package (MAL-2026-16394) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in envparse2 (npm)

MAL-2026-16394

Immediate action

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

npm uninstall envparse2

What this malware does

On require() of the package's main entry and on invocation of the dot2env CLI, the module reads the bundled dist/stest.jpg, parses JPEG markers, and extracts a UTF-8 string from the APP13 (0xED) segment. The extracted string is passed as an argument to powershell.exe -NoProfile -NonInteractive -EncodedCommand, launched hidden on Windows via a VBS relay dropped to %TMP% and invoked through wscript.exe. The invocation is assembled from split string fragments (['power','shell','.exe'].join(''), -Encoded+Command, wscript+.exe) to hide the command from static scanners, and identifiers use a telemetry/analytics cover story (telemetryFs, dispatchAnalytics, analyticsEnvelope, scanMetricFrame). Execution is triggered unconditionally by a top-level const {dispatchAnalytics:Re}=T(); Re(); in dist/index.cjs. The bundle also embeds a package.json fragment declaring name: 'node-env-buffer', version: '2.2.6' while the tarball is published as [email protected], indicating a renamed republish under a dotenv-style cover identity. The 287 KB JPEG has no legitimate role in a dotenv-style library; it is a container for the executable payload.

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

1 flagged

1.0.1

Indicators of compromise (SHA-256)

438952ae1e11ed7118f698ec2f5a31caa0af6dd843115a02ba9515a7fc5c21ff

59aed7381a2a7026336f5e79671e05e9313688533ca35e15cf7010a975c2c897

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for envparse2 (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging envparse2 across your stack and pipelines.
If you installed it — respond
Remove envparse2 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.
Did it already run?
If envparse2 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks envparse2 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. envparse2 on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-q747-c2cv-gfhjIN-MAL-2026-020300

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks envparse2-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database