streak-metricsanpm
Advisory published Updated
streak-metricsa is a confirmed malicious npm package (MAL-2026-12470) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in streak-metricsa (npm)
What this malware does
[email protected] presents itself as a calendar-day math helper but its main entry (dist/index.mjs, the default exports target) embeds a Linux x86-64 ELF binary as a base64-chunk array assigned to a variable named _. At module top level — reached on any import/require of the package — the chunks are joined via Buffer.concat and Buffer.from(b,'base64'), written to disk, chmod'd 0o755, and executed via node:child_process. The dropped ELF's dynamic symbols include SSL_connect / SSL_read / SSL_write / TLS_client_method, socket / getaddrinfo, dlopen / dlsym, popen, execl / execv, fork, pthread_create, kill, and mkdtemp — the shape of a TLS-based remote-command implant. The README describes the top-level behavior as a tiny startup self-check, which does not match a native binary drop-and-execute. Any consumer that imports streak-metricsa gains an executing native implant on the host with outbound TLS and shell-exec capability.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for streak-metricsa (version 1.0.0).
If you installed it — respond
Remove streak-metricsa 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.
Did it already run?
If streak-metricsa was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks streak-metricsa-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.