Which versions of streamlinear are malicious?

The following npm versions of streamlinear are flagged malicious: 2.3.7. Treat any of these as compromised.

How do I remediate streamlinear if I installed it?

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

If streamlinear 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.

Is streamlinear part of a known attack campaign?

Yes — streamlinear is associated with the RLMA-2025-06491 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 streamlinear across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for streamlinear (version 2.3.7).

Malicious package

streamlinearnpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

streamlinear is a confirmed malicious npm package (MAL-2025-192865) that executes malicious code on install (malicious version 2.3.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in streamlinear (npm)

MAL-2025-192865

Immediate action

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

npm uninstall streamlinear

What this malware does

The package streamlinear was found to contain malicious code.

Malicious versions

1 flagged

2.3.7

Indicators of compromise (SHA-256)

a24399e6ec8505155cf41608e62cccd451af8ab3672e840c679066e044ebc627

8323a6d59780062d501afa4c8c71b623107bdb0b96cdbe909ec5d01fc76febfd

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for streamlinear (version 2.3.7).
If you installed it — respond
Remove streamlinear 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 streamlinear 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

No. streamlinear on npm has been identified as a malicious package (version 2.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06491

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks streamlinear-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