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

statist-browser-typed-client-mb.reliability.android.metricsnpm

statist-browser-typed-client-mb.reliability.android.metrics is a confirmed malicious npm package (MAL-2026-12449) that executes malicious code on install (malicious version 20.9.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in statist-browser-typed-client-mb.reliability.android.metrics (npm)

MAL-2026-12449
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall statist-browser-typed-client-mb.reliability.android.metrics

What this malware does

On require() of the package, index.js loads loader.js which downloads a platform-specific binary from hardcoded Cloudflare Workers hosts assembled by string-array joins (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), with a base64-chunked DNS-TXT covert-channel fallback via *.dl.well1.site. The fetched bytes are written to /tmp or %TEMP% under disguised filenames (dotnet_diag<rand>.exe,.cache_<rand>), chmodded 0o755, and spawned detached via cmd.exe or /bin/sh. Destination hostnames are fragmented across string arrays and joined at runtime to defeat static string matching, and an environment-variable opt-out check is used to evade sandboxes. The package advertises itself as a telemetry exporter but ships a fetch-and-execute dropper reachable on import.

Malicious versions

1 flagged
20.9.3

Indicators of compromise (SHA-256)

452d03d6ed4b82fa956dc7419066742e9c91518b786f0e164aa63e2ae55d6083

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for statist-browser-typed-client-mb.reliability.android.metrics (version 20.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging statist-browser-typed-client-mb.reliability.android.metrics across your stack and pipelines.

  2. If you installed it — respond

    Remove statist-browser-typed-client-mb.reliability.android.metrics 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.

  3. Did it already run?

    If statist-browser-typed-client-mb.reliability.android.metrics 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 statist-browser-typed-client-mb.reliability.android.metrics 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. statist-browser-typed-client-mb.reliability.android.metrics on npm has been identified as a malicious package (version 20.9.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014734

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks statist-browser-typed-client-mb.reliability.android.metrics-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.

Explore

statist-browser-typed-client-mb.reliability.android.metrics (npm) malicious package — MAL-2026-12449 | O3 Security