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

0ctf-chalwebnpm

Malicious code in 0ctf-chalweb (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3667
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall 0ctf-chalweb

What this malware does

The package's entire content (xss.js) is a 2-line cookie-stealing payload that creates an Image element pointing to https://collaborator.gbrls.workers.dev/ with base64-encoded document.cookie appended. This is a textbook XSS cookie exfiltration primitive targeting an attacker-controlled Cloudflare Workers endpoint. Regardless of whether this was published as a CTF artifact, any consumer who installs and bundles this package into a web app will exfiltrate end-users' cookies. There is no legitimate use case for publishing a cookie-exfil snippet to the public npm registry.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

6d7a129ab6079febb92ceac3587af97653477bce8a65b8e85bfa5bcae0293b0d

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    0ctf-chalweb 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.

  3. Did it already run?

    If 0ctf-chalweb 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 0ctf-chalweb 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. 0ctf-chalweb on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002143

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks 0ctf-chalweb-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

0ctf-chalweb (npm) malicious package — MAL-2026-3667 | O3 Security