Which versions of insomnia-plugin-random-pick are malicious?

The following npm versions of insomnia-plugin-random-pick are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate insomnia-plugin-random-pick if I installed it?

insomnia-plugin-random-pick is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed insomnia-plugin-random-pick — how do I know if it already compromised me?

If insomnia-plugin-random-pick 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 insomnia-plugin-random-pick part of a known attack campaign?

Yes — insomnia-plugin-random-pick is associated with the GHSA-hwcw-cr45-5whf 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 insomnia-plugin-random-pick 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 insomnia-plugin-random-pick (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging insomnia-plugin-random-pick across your stack and pipelines.

Malicious package

insomnia-plugin-random-picknpm

Malicious code in insomnia-plugin-random-pick (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191111

Immediate action

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

npm uninstall insomnia-plugin-random-pick

What this malware does

The package insomnia-plugin-random-pick 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

ee373a7544fd4827eec7883787e1621b6966bc9aa3a86c28afc42de4bcd64078

223cb3897cabcdb8e9e9d0b6f5cfb0286af465ff149e93e207888f085216b30d

8717488a1afc3be853313a0f8f243fa748188c0b321d8c9096182cf59bfbb1ed

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for insomnia-plugin-random-pick (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging insomnia-plugin-random-pick across your stack and pipelines.
If you installed it — respond
insomnia-plugin-random-pick is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If insomnia-plugin-random-pick 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 insomnia-plugin-random-pick 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. insomnia-plugin-random-pick on npm has been identified as a malicious package (version 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hwcw-cr45-5whf

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks insomnia-plugin-random-pick-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring