Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

cc-raiesynpm

Malicious code in cc-raiesy (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192932
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cc-raiesy

What this malware does

The package cc-raiesy was found to contain malicious code.

The OpenSSF Package Analysis project identified 'cc-raiesy' @ 99.99.99 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
99.99.99

Indicators of compromise (SHA-256)

1f5952f5f09794bf5f5b6cd4c41299aec2f6df42b0628c9706419f2659e51316
d9156cfe8712328dc4de944c470b2da3184bc49c1c444febc9eccf20f1fd962f

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cc-raiesy (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cc-raiesy across your stack and pipelines.

  2. If you installed it — respond

    Remove cc-raiesy 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.

  3. Did it already run?

    If cc-raiesy 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.

  4. How O3 protects you

    O3 blocks cc-raiesy 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. cc-raiesy on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks cc-raiesy-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.

cc-raiesy (npm) malicious package — MAL-2025-192932 | O3 Security