Which versions of dotenv-embed are malicious?

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

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

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

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

Yes — dotenv-embed is associated with the GHSA-g7gf-xv5g-23vj, RLMA-2026-01248 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-embed 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-embed (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-embed across your stack and pipelines.

Malicious package

dotenv-embednpm

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

MAL-2026-589

Immediate action

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

npm uninstall dotenv-embed

What this malware does

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

eb5a7942b654b4da1fb16e67f19ca82b3b52c4fcce4db85e9d5596571651c6b7

6bbecb8b9bb96fcd71af0764df5106d8163ccb94c21960bf858383ab85d10308

5d8160356f0fe6e4649c5bd9913220aaa687dfbc8bd66e6cd80053bdc7e631b8

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-embed (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-embed across your stack and pipelines.
If you installed it — respond
Remove dotenv-embed 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-embed 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-embed 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-embed 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-g7gf-xv5g-23vjRLMA-2026-01248

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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