What does the cc-raiesy malware do?

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.

Which versions of cc-raiesy are malicious?

The following npm versions of cc-raiesy are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate cc-raiesy if I installed it?

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.

I already installed cc-raiesy — how do I know if it already compromised me?

If cc-raiesy was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find cc-raiesy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cc-raiesy (version 99.99.99).

Malicious package

cc-raiesynpm

Advisory published Dec 25, 2025Updated Jan 2, 2026

cc-raiesy is a confirmed malicious npm package (MAL-2025-192932) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cc-raiesy (npm)

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

Find it
Search your lockfiles and build artifacts for cc-raiesy (version 99.99.99).
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.
Did it already run?
If cc-raiesy was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database