Which versions of streak-metricazbd are malicious?

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

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

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

If streak-metricazbd 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-metricazbd part of a known attack campaign?

Yes — streak-metricazbd is associated with the IN-MAL-2026-011370 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-metricazbd 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-metricazbd (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-metricazbd across your stack and pipelines.

Malicious package

streak-metricazbdnpm

streak-metricazbd is a confirmed malicious npm package (MAL-2026-12001) 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-metricazbd (npm)

MAL-2026-12001

Immediate action

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

npm uninstall streak-metricazbd

What this malware does

On import of the package, dist/index.mjs runs an IIFE that copies a bundled Linux x86_64 ELF (dist/math-core.bin) to /tmp/sm-engine-runtime/math-core.bin and spawns it via child_process.spawn, framed as 'math-core engine calibration' and wrapped in an error-swallowing try/catch. The dropped binary is a full remote-access implant identifying itself as 'RedShell': it beacons to a hardcoded remote server at 217.60.77.63, accepts commands over that channel to execute arbitrary shell commands via /bin/sh and /bin/bash, provides SOCKS5 proxying and TCP port forwarding, downloads and executes additional ELF/shellcode payloads, installs systemd --user persistence disguised as 'svc-update.service', and exposes /ssh_keys, /creds, /dbfind, /env, /dataextract, and /download commands that harvest installer SSH keys, credentials, and arbitrary files and exfiltrate them in chunks via POST /api/extract-receive. Any host that imports this package hands full remote control and credential access to the operator of 217.60.77.63.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4875da8c750beede70a9031fdd1cf1aa402c49cd94da3abbcd1964a4160a271b

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-metricazbd (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-metricazbd across your stack and pipelines.
If you installed it — respond
streak-metricazbd 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-metricazbd 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-metricazbd 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-metricazbd 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-011370

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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