Which versions of params-valid-js are malicious?

The following npm versions of params-valid-js are flagged malicious: 1.0.0, 1.0.1, 1.0.3. Treat any of these as compromised.

How do I remediate params-valid-js if I installed it?

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

I already installed params-valid-js — how do I know if it already compromised me?

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

Yes — params-valid-js is associated with the IN-MAL-2026-006882, IN-MAL-2026-007028, RLMA-2026-05203, RLUA-2026-05590 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 params-valid-js 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 params-valid-js (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging params-valid-js across your stack and pipelines.

Malicious package

params-valid-jsnpm

params-valid-js is a confirmed malicious npm package (MAL-2026-5988) that typosquats a legitimate package to trick installs (malicious versions 1.0.0, 1.0.1, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in params-valid-js (npm)

MAL-2026-5988

Immediate action

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

npm uninstall params-valid-js

What this malware does

The package presents itself as 'Simplified HTTP request client' and copies identity metadata from Mikeal Rogers' legitimate request package (bugs URL http://github.com/request/request/issues, copied copyright header), but its only effective behavior is to launch a remote-code-execution dropper. The default export in index.js is a middleware function whose sole action is to spawn node lib/callers.js as a detached child with stdio: 'ignore' and child.unref(), allowing the dropper to continue running after the parent exits. lib/callers.js shadows process with a local object (const process = { env: { DEV_API_KEY: 'google.com', DEV_SECRET_KEY: 'x-secret-key', DEV_SECRET_VALUE: '_' } }) so what looks like environment configuration is actually a hardcoded fetch target. The script then performs axios.get(src, { headers: { [k]: v } }), reads response.data.Cookie, passes it to new Function.constructor('require', s), and immediately invokes the resulting function with the real require — executing whatever Node code the server returns with full module access. The combination of name/identity impersonation, detached background execution, environment-shadowing obfuscation, and unpinned remote-eval is a clear supply-chain attack: any consumer that loads this package and invokes the middleware export executes attacker-controlled code.

Malicious versions

3 flagged

1.0.01.0.11.0.3

Indicators of compromise (SHA-256)

4f0f4f5cc684f7bf7b40af2f6856c7d5865f57c7492da68af6c1c194741a4629

397af72237ba3626ac4727497662530f602c2ce6ec71406f48b508055687366c

f1f6fe16075c4c955e26afbb3715827410bb4a14505d75311879b306d42af437

22b041d947d7c306c08bdbba317f085958b61847f44e98bf79b0159e16cf47a4

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

Campaign

IN-MAL-2026-006882IN-MAL-2026-007028RLMA-2026-05203RLUA-2026-05590

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks params-valid-js-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