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

google-caja-bowernpm

google-caja-bower is a confirmed malicious npm package (MAL-2026-10186) that steals credentials and exfiltrates sensitive data (malicious versions 20.20.20, 999.20.20, 999.99.20…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in google-caja-bower (npm)

MAL-2026-10186
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall google-caja-bower

What this malware does

[email protected] declares scripts.preinstall = 'node index.js', so index.js runs automatically on npm install. index.js walks the installer's current working directory, builds a directory tree, enumerates up to 500 files (skipping only common binary/media extensions) up to 8MB each, and POSTs the tree plus each file's bytes as multipart uploads to two hardcoded Discord webhook URLs under discord.com/api/webhooks/. The payload also collects os.hostname(), process.env.USER / process.env.USERNAME, os.platform(), and process.cwd() and includes them in the webhook messages. Because the file filter excludes only binary/media types, credential-bearing text files present in the working tree (.env,.npmrc, ssh configs, cloud credentials, source code) are uploaded verbatim. The package name impersonates the Google Caja / Bower namespace and its own package description self-labels the behavior as 'collect and send system information to a remote endpoint'; the webhook message body identifies the campaign as 'Dependency Confusion Crawler'.

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

7 flagged
20.20.20999.20.20999.99.20999.999.201000.80.201000.800.201000.801.20

Indicators of compromise (SHA-256)

1a88566ebea62a22b812cbf3e7f192bd8487663d26884e8158c4dcff6cdaadee
460c81d727321ff0c483e6cddb1d9e6247e65531a084efbcbef2fd58d8152cec
5147954990c9d6f9c492648393cd14c7dfde6f36b220b7a644834f0f3489bd54
aeb7b0bb13638a837ac5521c602b3bbffc268935ac499f9c1af64cfe4bc765a0
ce6481e3117c0b891baf893802d3f8425a9914ce404036a0862d4e3848e49003
e34339f1be6afb8a41b6dbe2f7d7c480d5a438a67ff119b235d1d98ffa2b2e4a
f4258589d39bb6d7551b5731b0407d72c0c83e443dc8f9f40d43e4438a297378
4d307e63a5313eaae94ececb230bbd43410bc6fbd020b9f55d968bcb7f6c29f6

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 google-caja-bower (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging google-caja-bower across your stack and pipelines.

  2. If you installed it — respond

    google-caja-bower 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 google-caja-bower 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 google-caja-bower 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. google-caja-bower on npm has been identified as a malicious package (versions 20.20.20, 999.20.20, 999.99.20, 999.999.20, 1000.80.20, 1000.800.20, 1000.801.20 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009738IN-MAL-2026-009741IN-MAL-2026-009737IN-MAL-2026-009739IN-MAL-2026-009735IN-MAL-2026-009736IN-MAL-2026-009740GHSA-qq75-mfwc-v6gx

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

google-caja-bower (npm) malicious package — MAL-2026-10186 | O3 Security