Which versions of real-time-tweet-streamer are malicious?

The following npm versions of real-time-tweet-streamer are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate real-time-tweet-streamer if I installed it?

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

If real-time-tweet-streamer 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 real-time-tweet-streamer part of a known attack campaign?

Yes — real-time-tweet-streamer is associated with the GHSA-r69v-rwfw-jcv6, RLMA-2026-01538 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 real-time-tweet-streamer 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 real-time-tweet-streamer (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging real-time-tweet-streamer across your stack and pipelines.

Malicious package

real-time-tweet-streamernpm

Malicious code in real-time-tweet-streamer (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192422

Immediate action

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

npm uninstall real-time-tweet-streamer

What this malware does

The package real-time-tweet-streamer 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

1 flagged

0.1.0

Indicators of compromise (SHA-256)

174a710daf7afff555987c5ebed436e56b4430a4187ef310d3b41caa87c2a581

692b2a444eb479ec815e98413b99cd6cb677cf8be77edef431d8acf9d6c9e5c5

394d9dd930a7167c4b9bd9589fc310e9e03f2a56642308cb300d5f4875d30306

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

Campaign

GHSA-r69v-rwfw-jcv6RLMA-2026-01538

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks real-time-tweet-streamer-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