Which versions of dotenv-intend are malicious?

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

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

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

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

Yes — dotenv-intend is associated with the GHSA-623w-pf6v-gcgv, RLMA-2025-06114, RLUA-2026-01253 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-intend 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-intend (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-intend across your stack and pipelines.

Malicious package

dotenv-intendnpm

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

MAL-2025-192290

Immediate action

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

npm uninstall dotenv-intend

What this malware does

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

64a31dce3bccc8134695abbe65011f655e810a0a28726ce2d60668e3689ab605

2b29ae1386b4f6a14de72979eae00fc96b33b8a080975db5c8eb8917d23fdeff

b25be4f8fc2ec1c808f4438bd74cdff51b2582f4f2c0711bd04f0e86fd60bc40

459cd3ebefaf4d5d4da6c788cdd77a0640f7b447fb07d4ec2ff96e9df99e75d3

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-intend (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-intend across your stack and pipelines.
If you installed it — respond
Remove dotenv-intend 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-intend 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-intend 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-intend 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-623w-pf6v-gcgvRLMA-2025-06114RLUA-2026-01253

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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