Which versions of express-denv are malicious?

The following npm versions of express-denv are flagged malicious: 1.3.6. Treat any of these as compromised.

How do I remediate express-denv if I installed it?

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

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

Yes — express-denv is associated with the RLMA-2026-05081, RLUA-2026-06232 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 express-denv across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for express-denv (version 1.3.6).

Malicious package

express-denvnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

express-denv is a confirmed malicious npm package (MAL-2026-7283) that executes malicious code on install (malicious version 1.3.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in express-denv (npm)

MAL-2026-7283

Immediate action

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

npm uninstall express-denv

Malicious versions

1 flagged

1.3.6

Indicators of compromise (SHA-256)

0709f96c37cf9156f1a427eaaae73ec9f50e98c9a097c4e9869a6393d00a501c

70f6655372cb6421e3dfac75d1796907d495edcfe1c034a44e8436f911c757db

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for express-denv (version 1.3.6).
If you installed it — respond
Remove express-denv 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 express-denv 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. express-denv on npm has been identified as a malicious package (version 1.3.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05081RLUA-2026-06232

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks express-denv-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