Which versions of req-parmas-valid are malicious?

The following npm versions of req-parmas-valid are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate req-parmas-valid if I installed it?

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

I already installed req-parmas-valid — how do I know if it already compromised me?

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

Yes — req-parmas-valid is associated with the IN-MAL-2026-006879, RLMA-2026-05605 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 req-parmas-valid 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 req-parmas-valid (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging req-parmas-valid across your stack and pipelines.

Malicious package

req-parmas-validnpm

req-parmas-valid is a confirmed malicious npm package (MAL-2026-5991) that typosquats a legitimate package to trick installs (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in req-parmas-valid (npm)

MAL-2026-5991

Immediate action

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

npm uninstall req-parmas-valid

What this malware does

Package name req-parmas-valid impersonates the well-known request HTTP client (description copied verbatim as 'Simplified HTTP request client.', bugs.url points at github.com/request/request/issues, README and most source copied from upstream). Bolted onto the copied source is a malicious middleware export (also exposed as reqValidator and the package's default export) which spawns a detached node lib/callers.js child process. lib/callers.js performs an HTTPS GET to https://www.jsonkeeper.com/b/DDC6J (an anonymous, mutable paste host), reads the Cookie field of the JSON response, and evaluates it via new Function.constructor("require", s)(require) — handing the fetched bytes full Node require capability with no integrity check, no pinning, and a payload host completely alien to the package's advertised purpose. Any consumer that imports and uses the middleware (the obvious Express-style API shape) executes arbitrary remote code controlled by whoever currently owns the paste.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

063b7e2667c434784d0b5d2ce333ea700fbc17571da3f5f4fc7d0f03ac406bd0

ab33e727b3338f40fbe82e666b8d9bcf12a47e8a6cb9492bcfaca66766500f65

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

Campaign

IN-MAL-2026-006879RLMA-2026-05605

References

npmjs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks req-parmas-valid-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