Which versions of jest-node-paramset are malicious?

Every published version of jest-node-paramset on npm is considered malicious. Remove the package entirely.

How do I remediate jest-node-paramset if I installed it?

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

If jest-node-paramset 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 jest-node-paramset part of a known attack campaign?

Yes — jest-node-paramset is associated with the GHSA-jwcf-6pvx-4cwr 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 jest-node-paramset 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 jest-node-paramset (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jest-node-paramset across your stack and pipelines.

Malicious package

jest-node-paramsetnpm

Malicious code in jest-node-paramset (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1045

Immediate action

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

npm uninstall jest-node-paramset

What this malware does

The package jest-node-paramset was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

eb14eafef7d31be0f6f654e6c69c8906f30ec1a23dca29210044f256340b2f42

0195409dba352b70324fae3226921105e7658404675e2b9e8ab1e898c5bd84fa

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for jest-node-paramset (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jest-node-paramset across your stack and pipelines.
If you installed it — respond
Remove jest-node-paramset 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 jest-node-paramset 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 jest-node-paramset 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. jest-node-paramset on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jwcf-6pvx-4cwr

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks jest-node-paramset-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