Which versions of express-guardrail are malicious?

The following npm versions of express-guardrail are flagged malicious: 1.3.5, 1.4.1. Treat any of these as compromised.

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

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

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

Yes — express-guardrail is associated with the GHSA-62qq-cf7w-23hx, RLMA-2026-05083, RLUA-2026-06234 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-guardrail across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for express-guardrail (2 malicious versions).

Malicious package

express-guardrailnpm

Advisory published Jul 6, 2026Updated Sep 1, 2026

express-guardrail is a confirmed malicious npm package (MAL-2026-6821) that executes malicious code on install (malicious versions 1.3.5, 1.4.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in express-guardrail (npm)

MAL-2026-6821

Immediate action

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

npm uninstall express-guardrail

What this malware does

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

2 flagged

1.3.51.4.1

Indicators of compromise (SHA-256)

40e91ddac990897c8c43891c5abf64696a0e9d9d4b168e7a6e5f4a827e4f040d

d5138d96ec337800912ca44352e7483563112b85521d6d0f7763e86f755bfa39

3d4dba5457c3e55e151377157044162298ebdd2412a80a7c7f13f4802edf74a5

Detection & response playbook

Malicious package

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

Campaign

GHSA-62qq-cf7w-23hxRLMA-2026-05083RLUA-2026-06234

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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