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

@cats-cdf/browser-metrics-meternpm

@cats-cdf/browser-metrics-meter is a confirmed malicious npm package (MAL-2026-13479) that steals credentials and exfiltrates sensitive data (malicious versions 2.0.0, 3.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @cats-cdf/browser-metrics-meter (npm)

MAL-2026-13479
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @cats-cdf/browser-metrics-meter

What this malware does

The package's preinstall lifecycle script runs automatically on npm install and executes whoami and hostname, then fetches the machine's public IP from ifconfig.me and transmits all three values as query-string parameters to a hardcoded out-of-band interaction domain (kwphewvexhjbtfduscqybx6q7c862eh0g.oast.fun) over plain HTTP via curl, with a wget fallback. The domain is an OAST (out-of-band application security testing) collector used to receive exfiltrated reconnaissance data. The behavior fires unconditionally with no first-party relationship, no consent, and no documented purpose consistent with the package name.

Malicious versions

2 flagged
2.0.03.1.1

Indicators of compromise (SHA-256)

1617d21e0e87913cb47a2bdf2c2f9e010d8eb91de61b74e692ee8bac8299ba94
83df5c7e17dd2b9a808bddee17deb157e88a12632a632177f7969fce9ccfa7a8

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 @cats-cdf/browser-metrics-meter (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @cats-cdf/browser-metrics-meter across your stack and pipelines.

  2. If you installed it — respond

    @cats-cdf/browser-metrics-meter 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 @cats-cdf/browser-metrics-meter 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 @cats-cdf/browser-metrics-meter 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. @cats-cdf/browser-metrics-meter on npm has been identified as a malicious package (versions 2.0.0, 3.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016846IN-MAL-2026-016848

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @cats-cdf/browser-metrics-meter-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

@cats-cdf/browser-metrics-meter (npm) malicious package — MAL-2026-13479 | O3 Security