Which versions of bulktweetbyref are malicious?

The following PyPI versions of bulktweetbyref are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate bulktweetbyref if I installed it?

bulktweetbyref is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed bulktweetbyref — how do I know if it already compromised me?

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

Yes — bulktweetbyref is associated with the RLMA-2025-03555, 2025-06-bulktweetbyref, RLUA-2026-00161 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 bulktweetbyref 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 bulktweetbyref (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 bulktweetbyref across your stack and pipelines.

Malicious package

bulktweetbyrefPyPI

Malicious code in bulktweetbyref (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6470

Immediate action

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

pip uninstall bulktweetbyref

What this malware does

Using the function simulates some behavior, but then download and runs an Infostealer

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-06-bulktweetbyref

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware
infostealer

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

cc17a758efb55184f78eaea608bb6c116129e75817337ec22401cdb5866f9b09

37f9a6adf2f6bceb8d49b86e00e8fd1d6303e73370f5d9620bfe678dd12525df

b6e44fa722cba73a0757878305b8641ff0539e6c32ffff20b9484ce39ce6a1aa

d00b2c8787d63545a7825835db960ce79bb2e2b2c952323eeb2d8e292d4977e1

b71f763feda620fb8a04ef988df6ca000b618e0187de9b2aa2989069c0ed33c2

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bulktweetbyref (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 bulktweetbyref across your stack and pipelines.
If you installed it — respond
bulktweetbyref is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bulktweetbyref 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 bulktweetbyref 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. bulktweetbyref on PyPI 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

RLMA-2025-035552025-06-bulktweetbyrefRLUA-2026-00161

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks bulktweetbyref-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring