Which versions of ajenti-plugin-testing-pyld are malicious?

The following PyPI versions of ajenti-plugin-testing-pyld are flagged malicious: 0.0.1, 0.99.999, 1.1.1. Treat any of these as compromised.

How do I remediate ajenti-plugin-testing-pyld if I installed it?

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

If ajenti-plugin-testing-pyld 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 ajenti-plugin-testing-pyld part of a known attack campaign?

Yes — ajenti-plugin-testing-pyld is associated with the GENERIC-simple-tests 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 ajenti-plugin-testing-pyld 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 ajenti-plugin-testing-pyld (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ajenti-plugin-testing-pyld across your stack and pipelines.

Malicious package

ajenti-plugin-testing-pyldPyPI

Malicious code in ajenti-plugin-testing-pyld (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-192392

Immediate action

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

pip uninstall ajenti-plugin-testing-pyld

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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: GENERIC-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

3 flagged

0.0.10.99.9991.1.1

Indicators of compromise (SHA-256)

8f75e248c6b93183d9fb3295781e0ffda38ca1afa25cefb866205312f2a78cfd

c9f06b3dac61d0bab3271459da521514201b4b69826b7edd9a33d793e870e03f

d21d0d38383da324a45399ec777f707a273e0261264c43bab20431eda37f951d

4c039df8ba9e4f40162ee73b3cf93b5ea41f16caf89cee8f99b94124cf227a99

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ajenti-plugin-testing-pyld (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ajenti-plugin-testing-pyld across your stack and pipelines.
If you installed it — respond
Remove ajenti-plugin-testing-pyld 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 ajenti-plugin-testing-pyld 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 ajenti-plugin-testing-pyld 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. ajenti-plugin-testing-pyld on PyPI has been identified as a malicious package (versions 0.0.1, 0.99.999, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-simple-tests

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks ajenti-plugin-testing-pyld-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