Which versions of bulktweetplus are malicious?

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

How do I remediate bulktweetplus if I installed it?

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

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

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

Malicious package

bulktweetplusPyPI

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

MAL-2025-6471

Immediate action

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

pip uninstall bulktweetplus

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)

47fb1215e3eeda89cfcc7ad00da4a0180d569339a71a6179b6dbf6a8665ecdb8

397afb7be38d5df8c771e8f54a230fe8d2e1f6632fc83039e63c3b7b0eef862b

3f66a670d67e37fec4746d5aaf53be9e2f5267c68b667f1becdb55f8d75ce70a

2beb52e86cfea789dfd951d11b96b89fd9f427f7360abf39dfc97d4573e53f29

c178a4cc400029c1d6f19a3e844cf30d35b52a2d302f08211bbe6d91b4290d91

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 bulktweetplus (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 bulktweetplus across your stack and pipelines.
If you installed it — respond
bulktweetplus 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 bulktweetplus 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 bulktweetplus 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. bulktweetplus 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-035562025-06-bulktweetbyrefRLUA-2026-00162

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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