Which versions of dotjsenv are malicious?

The following npm versions of dotjsenv are flagged malicious: 1.1.7. Treat any of these as compromised.

How do I remediate dotjsenv if I installed it?

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

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

Yes — dotjsenv is associated with the GHSA-63qm-964q-w2w5, RLMA-2026-01262 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 dotjsenv 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 dotjsenv (version 1.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dotjsenv across your stack and pipelines.

Malicious package

dotjsenvnpm

Malicious code in dotjsenv (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192755

Immediate action

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

npm uninstall dotjsenv

What this malware does

The package dotjsenv 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

1.1.7

Indicators of compromise (SHA-256)

b4dd239728dde802ec7a7aadd85d2a9f1c5c3e8b83e5f19b92a2afab16d1cd1c

199e0e242516cf235f3d4f4d7b7921f7b52573e674bd76da515939782a81c153

713eaa1e2dee9ccb6d95848f0bef3112002a8f4f084066fe537f97154317f9c4

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

Campaign

GHSA-63qm-964q-w2w5RLMA-2026-01262

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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