Which versions of dotevn are malicious?

The following npm versions of dotevn are flagged malicious: 17.2.1. Treat any of these as compromised.

How do I remediate dotevn if I installed it?

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

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

Yes — dotevn is associated with the RLMA-2025-04989, RLUA-2025-05769 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 dotevn 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 dotevn (version 17.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dotevn across your stack and pipelines.

Malicious package

dotevnnpm

dotevn is a confirmed malicious npm package (MAL-2025-44063) that executes malicious code on install (malicious version 17.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dotevn (npm)

MAL-2025-44063

Immediate action

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

npm uninstall dotevn

What this malware does

The package dotevn was found to contain malicious code.

Malicious versions

1 flagged

17.2.1

Indicators of compromise (SHA-256)

efa0c2d8cfbc42b24a9912b6c0df7a6eb6a5b2774a18b194e47679c84821eef7

738480b98885c0854f054d3aec0d950ac5b6a291556a3b29ed2215467f14a2c4

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

Campaign

RLMA-2025-04989RLUA-2025-05769

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dotevn-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

Explore

All malware advisories How O3 detects malware Vulnerability database