envforge3@1.0.1

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.