Which versions of dotenv-expanded are malicious?

The following npm versions of dotenv-expanded are flagged malicious: 3.3.5. Treat any of these as compromised.

How do I remediate dotenv-expanded if I installed it?

Remove dotenv-expanded 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.

I already installed dotenv-expanded — how do I know if it already compromised me?

If dotenv-expanded 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 dotenv-expanded part of a known attack campaign?

Yes — dotenv-expanded is associated with the GHSA-94jw-vmxc-vv4v, RLMA-2026-01250 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 dotenv-expanded 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 dotenv-expanded (version 3.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dotenv-expanded across your stack and pipelines.

Malicious package

dotenv-expandednpm

Malicious code in dotenv-expanded (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-415

Immediate action

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

npm uninstall dotenv-expanded

What this malware does

The package dotenv-expanded was found to contain malicious code.

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

3.3.5

Indicators of compromise (SHA-256)

8c545865cdbec4a05b0f51103dd3560d60c3f43b818465e4a935a47bf84078d2

e9e36cd005779e12b645b7ec5f6e65df1edae7c6d86736507cd1feacec1ef7cf

15375af632a499e3c08b9c1710fcd73c19e34795c616b5f283925e86442ee633

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dotenv-expanded (version 3.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dotenv-expanded across your stack and pipelines.
If you installed it — respond
Remove dotenv-expanded 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.
Did it already run?
If dotenv-expanded 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 dotenv-expanded 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. dotenv-expanded on npm has been identified as a malicious package (version 3.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-94jw-vmxc-vv4vRLMA-2026-01250

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dotenv-expanded-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.

Malware detection Runtime egress monitoring