Malicious code in envforge3 (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-16393
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3770550d6db043006c8b2aa75dcac951db1cd9eb7494b0259d7eb69d28f26e32) 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. ## Source: ghsa-malware (ea995ab68fd67e3149b5e7115e80c462539377778424ae3c13155b469bdda3e1) 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.
- Source published
- 22 Sep 2026 18:22:20 UTC
- Source modified
- 22 Sep 2026 22:30:05 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.