Which versions of dotenv-extend are malicious?

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

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

Remove dotenv-extend 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-extend — how do I know if it already compromised me?

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

Yes — dotenv-extend is associated with the GHSA-jr68-9xqf-rp8q, RLMA-2026-01251 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-extend 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-extend (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-extend across your stack and pipelines.

Malicious package

dotenv-extendnpm

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

MAL-2025-192743

Immediate action

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

npm uninstall dotenv-extend

What this malware does

The package dotenv-extend 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)

7ef0bc2453e5610efd0011a08cecb1021a4d5a38aee276a269ad3185bb40925a

b36b33fa03b9dafefe167d7891f649dc39ac77a18a67a25c44d0d647dd3518e9

45b0680450bdae4a5bf617ea9db459f5b4cf953f709747eec6ee7d06883bdfc2

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-extend (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-extend across your stack and pipelines.
If you installed it — respond
Remove dotenv-extend 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-extend 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-extend 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-extend 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-jr68-9xqf-rp8qRLMA-2026-01251

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dotenv-extend-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