streak-map-metricsnpm
streak-map-metrics is a confirmed malicious npm package (MAL-2026-11999) 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-map-metrics (npm)
What this malware does
The package's main module dist/index.mjs, executed on any import or require of the package, concatenates an array of base64-encoded fragments into a Linux x86-64 ELF binary and passes it to helpers in dist/internal/daymath.mjs that create a directory, write the file to disk, chmod it 0755, and spawn it detached with stdio ignored after a randomized delay. The helpers are labeled with calendar/cache-style names and JSDoc ('Ensure directory exists', 'Save data to cache', 'Start a background task') while their bodies dynamically import node:fs and node:child_process to perform the drop-and-run. The decoded ELF64 targets /lib64/ld-linux-x86-64.so.2 and imports TLS_client_method, SSL_CTX_new, SSL_connect, SSL_read, SSL_write, socket, bind, listen, getaddrinfo, gethostbyname, fork, setsid, dup2, execl, execv, and pthread_create — the shape of a TLS-based remote-shell implant that grants a remote peer command execution on the installer's host. The ELF is split into ~260-character base64 slices to defeat single-string signatures, and the README's 'tiny startup self-check, no postinstall' framing masks the import-time drop-and-execute.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for streak-map-metrics (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-map-metrics across your stack and pipelines.
If you installed it — respond
Remove streak-map-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.
Did it already run?
If streak-map-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.
How O3 protects you
O3 blocks streak-map-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks streak-map-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.