Which versions of @zzzgenesis00/env-loader are malicious?

The following npm versions of @zzzgenesis00/env-loader are flagged malicious: 4.2.0. Treat any of these as compromised.

How do I remediate @zzzgenesis00/env-loader if I installed it?

@zzzgenesis00/env-loader 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 @zzzgenesis00/env-loader — how do I know if it already compromised me?

If @zzzgenesis00/env-loader 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 @zzzgenesis00/env-loader part of a known attack campaign?

Yes — @zzzgenesis00/env-loader is associated with the IN-MAL-2026-014394 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 @zzzgenesis00/env-loader 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 @zzzgenesis00/env-loader (version 4.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zzzgenesis00/env-loader across your stack and pipelines.

Malicious package

@zzzgenesis00/env-loadernpm

@zzzgenesis00/env-loader is a confirmed malicious npm package (MAL-2026-12120) that steals credentials and exfiltrates sensitive data (malicious version 4.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zzzgenesis00/env-loader (npm)

MAL-2026-12120

Immediate action

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

npm uninstall @zzzgenesis00/env-loader

What this malware does

On npm install, postinstall.js reads installer-owned secret material — ~/.ssh entries, ~/.npmrc, ~/.gitconfig — and iterates a curated list of credential and wallet environment variables (NPM_TOKEN, GITHUB_TOKEN, AWS_SECRET_ACCESS_KEY, PRIVATE_KEY, MNEMONIC, SEED_PHRASE, ETHEREUM/BITCOIN/SOLANA/TRON_PRIVATE_KEY, WALLET_PRIVATE_KEY, API_KEY, etc.), enumerates Chrome/Firefox profile artifacts (Cookies, Login Data) and wallet directories, and runs npm whoami and git config user.email to identify the host. The collected payload is JSON-encoded and transmitted to two hardcoded, attacker-controlled destinations: a Telegram Bot API endpoint (api.telegram.org/bot<redacted>/sendMessage) and an HTTP POST to 40f955f39128bd79-178-249-214-24.servousercontent.com/collect. The package presents itself as a dotenv alternative and exports a stub wallet API (generateMnemonic, createWallet, signTransaction returning random bytes) as a cover story; the block-worthy behavior is the install-time credential theft in postinstall.js.

Malicious versions

1 flagged

4.2.0

Indicators of compromise (SHA-256)

cfbfc9bcbea1e1b9d6c52e2585bf5b28064fe8e38fe53304450fe1fd19340f3b

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 @zzzgenesis00/env-loader (version 4.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zzzgenesis00/env-loader across your stack and pipelines.
If you installed it — respond
@zzzgenesis00/env-loader 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 @zzzgenesis00/env-loader 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 @zzzgenesis00/env-loader 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. @zzzgenesis00/env-loader on npm has been identified as a malicious package (version 4.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014394

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @zzzgenesis00/env-loader-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