Which versions of 4meme-readable-stream are malicious?

Every published version of 4meme-readable-stream on npm is considered malicious. Remove the package entirely.

How do I remediate 4meme-readable-stream if I installed it?

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

If 4meme-readable-stream 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 4meme-readable-stream part of a known attack campaign?

Yes — 4meme-readable-stream is associated with the GHSA-3jxh-2g2c-p84h 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 4meme-readable-stream 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 4meme-readable-stream (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging 4meme-readable-stream across your stack and pipelines.

Malicious package

4meme-readable-streamnpm

Malicious code in 4meme-readable-stream (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-149904

Immediate action

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

npm uninstall 4meme-readable-stream

What this malware does

The package 4meme-readable-stream was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

00873aefefb0a26b8c5d392787620c7838d157b01f0a267cd67fc0cdd0a06e99

0bf6d930ea2c0ad7b353677dfafdbe18356b2cb350a496f593dfd2a284b6ec3e

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 4meme-readable-stream (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging 4meme-readable-stream across your stack and pipelines.
If you installed it — respond
Remove 4meme-readable-stream 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 4meme-readable-stream 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 4meme-readable-stream 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. 4meme-readable-stream on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3jxh-2g2c-p84h

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks 4meme-readable-stream-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