Which versions of bugscanx are malicious?

The following PyPI versions of bugscanx are flagged malicious: 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.2.0, 1.2.1, 1.2.2. Treat any of these as compromised.

How do I remediate bugscanx if I installed it?

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

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

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

Search your lockfiles and build artifacts for bugscanx (12 malicious versions).

Malicious package

bugscanxPyPI

bugscanx is a confirmed malicious PyPI package (MAL-2025-904) that executes malicious code on install (malicious versions 1.0.1, 1.0.2, 1.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bugscanx (PyPI)

MAL-2025-904

Immediate action

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

pip uninstall bugscanx

Malicious versions

12 flagged

1.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.91.2.01.2.11.2.2

Indicators of compromise (SHA-256)

0725d91aa6febaacf723331aa99237067e21307af33165f0f884c15a623333f7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bugscanx (12 malicious versions).
If you installed it — respond
Remove bugscanx 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 bugscanx 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. bugscanx on PyPI has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, and 4 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-00442

Credits

ReversingLabs · finder

Detect & block this

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