Which versions of envforge3 are malicious?

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

How do I remediate envforge3 if I installed it?

envforge3 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 envforge3 — how do I know if it already compromised me?

If envforge3 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 envforge3 part of a known attack campaign?

Yes — envforge3 is associated with the GHSA-7chm-5cxc-2wx2, IN-MAL-2026-020302 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 envforge3 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 envforge3 (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 envforge3 across your stack and pipelines.

Malicious package

envforge3npm

envforge3 is a confirmed malicious npm package (MAL-2026-16393) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in envforge3 (npm)

MAL-2026-16393

Immediate action

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

npm uninstall envforge3

What this malware does

On require() of the package's main entry, dist/index.cjs invokes dispatchAnalytics() at module top level. That routine reads dist/stest.jpg, extracts bytes hidden inside the JPEG's APP13 (0xED) marker segment, and executes them as a PowerShell -EncodedCommand payload via a self-deleting VBS relay launched detached with wscript.exe on Windows. The token strings 'powershell.exe', '-NoProfile', '-NonInteractive', '-EncodedCommand' and 'wscript.exe' are assembled via array.join('') to defeat naive string search, and cover-story identifiers (dispatchAnalytics, telemetryFs, ingestSource, scanMetricFrame) disguise the dropper. dist/decode.js is a readable copy of the same logic. The published package.json declares name envforge3 version 1.0.1, but the metadata embedded inside dist/cli.cjs identifies the payload as node-env-buffer v2.2.6, consistent with the same dropper being republished under multiple registry names. Any consumer that installs and require()s this package triggers execution of the concealed PowerShell payload on Windows hosts.

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)

ea995ab68fd67e3149b5e7115e80c462539377778424ae3c13155b469bdda3e1

3770550d6db043006c8b2aa75dcac951db1cd9eb7494b0259d7eb69d28f26e32

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for envforge3 (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 envforge3 across your stack and pipelines.
If you installed it — respond
envforge3 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 envforge3 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 envforge3 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. envforge3 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-7chm-5cxc-2wx2IN-MAL-2026-020302

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks envforge3-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