Which versions of request-easy-validator are malicious?

The following npm versions of request-easy-validator are flagged malicious: 1.0.6, 1.0.7, 1.1.0, 1.2.0, 1.2.1. Treat any of these as compromised.

How do I remediate request-easy-validator if I installed it?

request-easy-validator is a typosquat — you almost certainly intended a legitimately-named package. Remove request-easy-validator, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed request-easy-validator — how do I know if it already compromised me?

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

Yes — request-easy-validator is associated with the RLMA-2026-02035, IN-MAL-2026-003458, IN-MAL-2026-003457 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 request-easy-validator 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 request-easy-validator (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging request-easy-validator across your stack and pipelines.

Malicious package

request-easy-validatornpm

Malicious code in request-easy-validator (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2798

Immediate action

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

npm uninstall request-easy-validator

What this malware does

request-easy-validator impersonates the popular request package (cloned README, bugs URL points at github.com/request/request, source is a fork of request) and ships a hidden remote-code-execution dropper. index.js exports a middleware function (also exposed as default, .reqValidator, and .request) that, on any invocation by the consumer, spawns a detached node lib/callers.js child with stdio: 'ignore' and child.unref() to hide it from the parent process. lib/callers.js then issues an HTTPS GET to https://jsonkeeper.com/b/PWEH9 (an anonymous, mutable, attacker-controlled paste host) with header x-secret-key: _, takes the .Cookie field from the response, and passes it to new Function.constructor('require', s) invoked with the live require — granting the paste-host operator arbitrary Node.js code execution with full module access on any server using this package. The payload URL is mutable, so the attacker can change the executed code at any time without republishing the package.

Malicious versions

5 flagged

1.0.61.0.71.1.01.2.01.2.1

Indicators of compromise (SHA-256)

8edcb2f860332561b7d9050d2ce2e2dcb82eecbbc51dc8c659ca4e741f70de1b

f6016a67de1924ce3156de3c59cb6f311ad9fe0151c129cd63dc56007576a369

59057b0a6f845ac1e8bfa571c4e26295e469abdd5c6faa2e68007ef78816ec9b

59c86157ff92828c8f05107e9b16169821d937ef657d7fcbb19d6862242c07af

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for request-easy-validator (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging request-easy-validator across your stack and pipelines.
If you installed it — respond
request-easy-validator is a typosquat — you almost certainly intended a legitimately-named package. Remove request-easy-validator, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If request-easy-validator 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 request-easy-validator 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. request-easy-validator on npm has been identified as a malicious package (versions 1.0.6, 1.0.7, 1.1.0, 1.2.0, 1.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02035IN-MAL-2026-003458IN-MAL-2026-003457

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks request-easy-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