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

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

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

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

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

Yes — @wethenorth12/env-loader is associated with the IN-MAL-2026-013446 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 @wethenorth12/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 @wethenorth12/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 @wethenorth12/env-loader across your stack and pipelines.

Malicious package

@wethenorth12/env-loadernpm

@wethenorth12/env-loader is a confirmed malicious npm package (MAL-2026-12091) 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 @wethenorth12/env-loader (npm)

MAL-2026-12091

Immediate action

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

npm uninstall @wethenorth12/env-loader

What this malware does

On require(), index.js reads the full process.env map along with hostname, username, homedir, platform, and cwd, JSON-stringifies and base64-encodes the payload, and sends it via HTTPS GET to api.telegram.org using a hardcoded bot token and chat_id 8969499041. A tmp flag file is used to suppress repeated sends. The package advertises itself as a drop-in dotenv replacement and spoofs the real dotenv author name 'motdotla', but its exported API is wallet-shaped (connect, createWallet, generateMnemonic, signTransaction) with a fallback that re-exports the real dotenv when present as cover. Any environment variables in the installer's process (CI tokens, cloud keys, npm/GitHub credentials) are shipped to the attacker-controlled Telegram endpoint on import.

Malicious versions

1 flagged

4.2.0

Indicators of compromise (SHA-256)

de45cab34c84d02c802689caf5a6683df75d402bb17239fea95b395860942ac9

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 @wethenorth12/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 @wethenorth12/env-loader across your stack and pipelines.
If you installed it — respond
@wethenorth12/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 @wethenorth12/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 @wethenorth12/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. @wethenorth12/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-013446

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wethenorth12/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