Which versions of package-name-here are malicious?

The following PyPI versions of package-name-here are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate package-name-here if I installed it?

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

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

Yes — package-name-here is associated with the RLMA-2025-01982, GENERIC-simple-tests, RLUA-2026-00581 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 package-name-here 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 package-name-here (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging package-name-here across your stack and pipelines.

Malicious package

package-name-herePyPI

Malicious code in package-name-here (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-2984

Immediate action

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

pip uninstall package-name-here

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

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

c236c4bb6fb6c330c14c90a417e0884e5bba06ea0bb85a31eaa9a1b16042f25c

6bc4558cbb72bfc09157c94f561cd25905b246922091a41067a14335274f3a0e

bef7ab75d289fdb44ea5f5d6b5df8cd1f77c7a728db1d4062e829ff91daa95be

7f198d91220287591ece575d17043bf9cb91c290b641b0cbcf3ffcf7a44e2048

7b08c7d0277ba72e73bf186eb6e99518acad66974b17309f2d2da1958a2a6d88

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 package-name-here (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging package-name-here across your stack and pipelines.
If you installed it — respond
Remove package-name-here 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 package-name-here 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 package-name-here 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. package-name-here on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-01982GENERIC-simple-testsRLUA-2026-00581

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks package-name-here-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