Which versions of streak-int-lib are malicious?

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

How do I remediate streak-int-lib if I installed it?

Remove streak-int-lib 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.

I already installed streak-int-lib — how do I know if it already compromised me?

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

Yes — streak-int-lib is associated with the IN-MAL-2026-014688, GHSA-266j-4pvf-xhwr 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-int-lib 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-int-lib (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-int-lib across your stack and pipelines.

Malicious package

streak-int-libnpm

streak-int-lib is a confirmed malicious npm package (MAL-2026-12467) 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-int-lib (npm)

MAL-2026-12467

Immediate action

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

npm uninstall streak-int-lib

What this malware does

[email protected] ships an x86-64 ELF binary as a base64 blob disguised as configuration data (defaultConfig.data joined into embeddedService in index.mjs). On module import, top-level code invokes initializeBackgroundService(), which decodes the blob, writes it to ~/.config/systemd/user/index with mode 0755, and spawns it via child_process.spawn with detached:true, stdio ignored, and proc.unref() so the native process outlives Node. The decoded binary contains TLS/networking symbols (SSL_write, SSL_connect, TLS_client_method, getaddrinfo, gethostname, setsid), indicating a network-capable backgrounded payload. Cover-story comments describe the side effect as a benign 'startup self-check' that 'touches no network and no filesystem', contradicting the observed behavior. The package's declared calendar-math purpose has no need for a bundled ELF or a systemd-path persistence artifact.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

0acd9bdc8d6474a54b3c985b8472cd50295130d12029de1a8a10175f9be8bb35

dffd7a66bce43c28a04ae46c2376eeb72996bc7b3a32391e28a157e9c3b11d88

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for streak-int-lib (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-int-lib across your stack and pipelines.
If you installed it — respond
Remove streak-int-lib 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-int-lib 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-int-lib 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-int-lib 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-014688GHSA-266j-4pvf-xhwr

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks streak-int-lib-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database