Which versions of express-http-validator are malicious?

The following npm versions of express-http-validator are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate express-http-validator if I installed it?

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

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

Yes — express-http-validator is associated with the RLMA-2026-01307 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-http-validator across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for express-http-validator (4 malicious versions).

Malicious package

express-http-validatornpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

express-http-validator is a confirmed malicious npm package (MAL-2026-1731) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in express-http-validator (npm)

MAL-2026-1731

Immediate action

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

npm uninstall express-http-validator

What this malware does

The package express-http-validator was found to contain malicious code.

Malicious versions

4 flagged

1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

92bdf981511c994111e1b68cd6a6ad61be6d43756342f476da18954ee197d87f

2471851d15cff5d3bc09d823660e1bebf3aee789535bf81e4f71c1ed6fa1fd86

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01307

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks express-http-validator-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