Which versions of dotenvx-ext are malicious?

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

How do I remediate dotenvx-ext if I installed it?

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

If dotenvx-ext was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is dotenvx-ext part of a known attack campaign?

Yes — dotenvx-ext is associated with the GHSA-rggj-8jcg-33c7, RLMA-2026-01260 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 dotenvx-ext across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dotenvx-ext (version 3.3.5).

Malicious package

dotenvx-extnpm

Advisory published Feb 24, 2026Updated Mar 19, 2026

dotenvx-ext is a confirmed malicious npm package (MAL-2026-1007) that executes malicious code on install (malicious version 3.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dotenvx-ext (npm)

MAL-2026-1007

Immediate action

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

npm uninstall dotenvx-ext

What this malware does

The package dotenvx-ext 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)

a3af4fb14756c0946c71147b11cfa0f09db31ba182c62938c62671d2c2059c8e

cb1944d5124a9fcb2f280723cad9c0c8116d155fc29444186a9e86bfb3609afc

d86f9292a7e07995d83ba2b88d3fe7492ab45f8e6eb851e030ae732bab595e15

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dotenvx-ext (version 3.3.5).
If you installed it — respond
Remove dotenvx-ext 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 dotenvx-ext was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dotenvx-ext 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-rggj-8jcg-33c7RLMA-2026-01260

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dotenvx-ext-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