Which versions of dotenv-embedded are malicious?

The following npm versions of dotenv-embedded are flagged malicious: 0.0.1-security, 3.3.5. Treat any of these as compromised.

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

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

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

Yes — dotenv-embedded is associated with the GHSA-v736-fhq8-mxhm, RLMA-2026-01249 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-embedded 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-embedded (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dotenv-embedded across your stack and pipelines.

Malicious package

dotenv-embeddednpm

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

MAL-2026-721

Immediate action

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

npm uninstall dotenv-embedded

What this malware does

The package dotenv-embedded 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

2 flagged

0.0.1-security3.3.5

Indicators of compromise (SHA-256)

bf0cfff747361e3a51fbd35f3018e05312b4bd030890362b89821789ab2adb51

07a4c23212d813ad58db347e1a5a152b003e1085b18036f047755d05de52fe0b

e2dce51cedcc3126d1a0b9eef96826f5b5b1ea40c36618c536c9f70c97338d4f

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

Campaign

GHSA-v736-fhq8-mxhmRLMA-2026-01249

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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