envforge3npm
Advisory published Updated
envforge3 is a confirmed malicious npm package (MAL-2026-16393) 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 envforge3 (npm)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for envforge3 (version 1.0.1).
If you installed it — respond
Remove envforge3 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 envforge3 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 envforge3-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.