Which versions of streak-metricsazb are malicious?

The following npm versions of streak-metricsazb are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate streak-metricsazb if I installed it?

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

If streak-metricsazb 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.

Is streak-metricsazb part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for streak-metricsazb (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 streak-metricsazb across your stack and pipelines.

Malicious package

streak-metricsazbnpm

streak-metricsazb is a confirmed malicious npm package (MAL-2026-12002) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in streak-metricsazb (npm)

MAL-2026-12002

Immediate action

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

npm uninstall streak-metricsazb

What this malware does

On import of the package's main entry, a top-level async IIFE in index.mjs (labelled 'ENGINE INITIALIZATION & CALIBRATION') copies the shipped file dist/cache.bin to os.tmpdir()/sm-engine-runtime/math-core.bin and spawns it via child_process.spawn. The dropped ELF is a full Linux implant containing a hardcoded C2 at 217.60.77.63, a SECURE_BEACON|...|REDSHELL beacon protocol, a remote-shell dispatcher invoking /bin/sh and /bin/bash on C2-supplied input, SOCKS5 proxy and TCP port-forwarding, staged payload execution via curl plus memfd/mktemp, and systemd --user persistence via svc-update.service. The implant exposes beacon commands /ssh_keys, /creds, /dbfind, /download, /upload, /dataextract, and /clipboard, and exfiltrates collected data through POST /api/extract-receive on the C2. The package advertises calendar and streak math primitives; the calibration/JIT wording in the surrounding comments is a cover story contradicted by the binary's contents.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bc4ea1b382140e833e01605ec5278b7a9a877aaaddd96ea9057efef2560b66b2

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for streak-metricsazb (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 streak-metricsazb across your stack and pipelines.
If you installed it — respond
streak-metricsazb 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 streak-metricsazb 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.
How O3 protects you
O3 blocks streak-metricsazb 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. streak-metricsazb 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-011371

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks streak-metricsazb-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