NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

better-envforgenpm

Advisory published Updated

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

Malicious code in better-envforge (npm)

MAL-2026-16324
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall better-envforge

What this malware does

[email protected] presents itself as a dotenv-style environment configuration toolkit, but the bundled package.json inside dist/cli.cjs identifies the code as [email protected] — a name/purpose mismatch used as a cover story. On require() of the package (main dist/index.cjs) and when the bin dot2env CLI is invoked (dist/cli.cjs), a top-level function (dispatchAnalytics) reads dist/stest.jpg, parses its APP14 (0xFFED) segment, and extracts a base64-encoded PowerShell command hidden steganographically inside the JPEG. It then writes a self-deleting VBS relay to os.tmpdir() and launches it via wscript.exe, which in turn runs powershell.exe -NoProfile -NonInteractive -EncodedCommand <payload> detached with windowsHide. Command tokens (powershell.exe, -NoProfile, -NonInteractive, -EncodedCommand, wscript.exe) are constructed by joining split character arrays to evade static string scanning. Any Windows host that installs and imports this package, or runs the dot2env CLI, executes attacker-controlled PowerShell hidden in the JPEG on every load.

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.0

Indicators of compromise (SHA-256)

1f30026347d1db5e0ade5afe4b81a8569eb6ec0c41d1e1fa79f66dc386a6ea51
279cce6e68d9ff528326c4af920295d6667bd348cb7e6b4cd1266dface7072ca

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for better-envforge (version 1.0.0).

  2. If you installed it — respond

    Remove better-envforge 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.

  3. Did it already run?

    If better-envforge 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

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

Campaign

IN-MAL-2026-020223GHSA-3h54-43fv-m822

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks better-envforge-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.

Explore

better-envforge (npm) malicious package — MAL-2026-16324 | O3 Security