Which versions of 6cc are malicious?

The following npm versions of 6cc are flagged malicious: 0.2.8. Treat any of these as compromised.

How do I remediate 6cc if I installed it?

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

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

Is 6cc part of a known attack campaign?

Yes — 6cc is associated with the IN-MAL-2026-002478 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 6cc across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 6cc (version 0.2.8).

Malicious package

6ccnpm

Advisory published May 12, 2026Updated May 13, 2026

6cc is a confirmed malicious npm package (MAL-2026-3675) that steals credentials and exfiltrates sensitive data (malicious version 0.2.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 6cc (npm)

MAL-2026-3675

Immediate action

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

npm uninstall 6cc

What this malware does

index.js executes on require as an IIFE that reassigns console.warn/error (and adds console.SL/FB/N) to forward arguments via fetch() to a hardcoded Telegram bot (989543891 with chat IDs -1001161709623/-1001433099398/-1001482347974), a hardcoded Slack webhook (T021S1VDCEB/B0221B6786T/UEUp2F6L4sOzKY5XcuI6WdZw), two Firebase RTDBs (iiilll.firebaseio.com, i----i.firebaseio.com), and imgbb. Any installer that requires this package has subsequent console output — which routinely contains stack traces, internal state, tokens, and PII — silently relayed out of process to attacker infrastructure. The 17,576-entry 3-letter alphabet array is used to generate opaque Firebase keys for the collection bucket, corroborating that this is maintained exfiltration infrastructure, not an accident. This is unambiguous installer-side harm with traced code evidence.

Malicious versions

1 flagged

0.2.8

Indicators of compromise (SHA-256)

4956159952af1b6af08b70ab219d7827988fae1fd82994f29090a1f2bf299094

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for 6cc (version 0.2.8).
If you installed it — respond
6cc 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 6cc 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. 6cc on npm has been identified as a malicious package (version 0.2.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002478

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks 6cc-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

Explore

All malware advisories How O3 detects malware Vulnerability database