Which versions of cyrpto are malicious?

The following npm versions of cyrpto are flagged malicious: 1.0.0, 1.0.2, 1.0.4. Treat any of these as compromised.

How do I remediate cyrpto if I installed it?

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

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

Yes — cyrpto is associated with the GHSA-4pxr-pch5-8x98, RLMA-2026-01230 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 cyrpto 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 cyrpto (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cyrpto across your stack and pipelines.

Malicious package

cyrptonpm

Malicious code in cyrpto (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-331

Immediate action

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

npm uninstall cyrpto

What this malware does

The package cyrpto 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

3 flagged

1.0.01.0.21.0.4

Indicators of compromise (SHA-256)

1e003c50bdddfa1368c5ed0e356acfab8b21a0d410f1d181471b88221a590cd9

88df3de403df4549d6cae9b1d508f683da4ed91d472a6020a40a3dbd6d5930fc

73bcb1ffd5bb6af10a621bd5bcccfcb69bc591193d793d7733d6a8d3236bbb04

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

Campaign

GHSA-4pxr-pch5-8x98RLMA-2026-01230

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks cyrpto-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