Which versions of larger-batch-ctr are malicious?

The following PyPI versions of larger-batch-ctr are flagged malicious: 94.6. Treat any of these as compromised.

How do I remediate larger-batch-ctr if I installed it?

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

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

Yes — larger-batch-ctr is associated with the 2024-11-byted-dast 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 larger-batch-ctr across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for larger-batch-ctr (version 94.6).

Part of a larger attack: 2024-11-byted-dast published 183 malicious packages. See the full campaign →

Malicious package

larger-batch-ctrPyPI

Advisory published Nov 6, 2024Updated Dec 12, 2025

larger-batch-ctr is a confirmed malicious PyPI package (MAL-2024-10636) that steals credentials and exfiltrates sensitive data (malicious version 94.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in larger-batch-ctr (PyPI)

MAL-2024-10636

Immediate action

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

pip uninstall larger-batch-ctr

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'larger-batch-ctr' @ 94.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

94.6

Indicators of compromise (SHA-256)

db4300765f1658c2aea7cd741a96b021a92337dbb97807c037e67e130f02ce59

9b6b046a55684780d0609349b820dbf03562e5a7c358958288dd3a8b413eeb70

656e9c562903fe04cc05fafcf53492252e227e586138c11099ab475fcde70aee

90239b7046a6028321dce6c59adf07d39cf4d65199b496f01162cc09ea7b9457

Detection & response playbook

Credential / info stealer

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

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks larger-batch-ctr-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

Explore

All malware advisories How O3 detects malware Vulnerability database