Which versions of beautifulsoup4-new are malicious?

The following PyPI versions of beautifulsoup4-new are flagged malicious: 4.12.11. Treat any of these as compromised.

How do I remediate beautifulsoup4-new if I installed it?

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

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

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

Search your lockfiles and build artifacts for beautifulsoup4-new (version 4.12.11).

Malicious package

beautifulsoup4-newPyPI

beautifulsoup4-new is a confirmed malicious PyPI package (MAL-2025-41624) that executes malicious code on install (malicious version 4.12.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in beautifulsoup4-new (PyPI)

MAL-2025-41624

Immediate action

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

pip uninstall beautifulsoup4-new

Malicious versions

1 flagged

4.12.11

Indicators of compromise (SHA-256)

ef1772d82330467f961558372dbc2d76fdce2ccfab43407cb6100d5a0a8a6c62

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for beautifulsoup4-new (version 4.12.11).
If you installed it — respond
Remove beautifulsoup4-new 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 beautifulsoup4-new 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. beautifulsoup4-new on PyPI has been identified as a malicious package (version 4.12.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04115

Credits

ReversingLabs · finder

Detect & block this

O3 blocks beautifulsoup4-new-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