Which versions of malware-test-pack-new are malicious?

The following PyPI versions of malware-test-pack-new are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate malware-test-pack-new if I installed it?

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

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

Yes — malware-test-pack-new is associated with the RLMA-2024-11083, GENERIC-simple-tests, RLUA-2026-00493 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 malware-test-pack-new 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 malware-test-pack-new (version 0.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging malware-test-pack-new across your stack and pipelines.

Malicious package

malware-test-pack-newPyPI

Malicious code in malware-test-pack-new (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11629

Immediate action

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

pip uninstall malware-test-pack-new

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

1 flagged

0.0.4

Indicators of compromise (SHA-256)

6b11574e21efead8eb9a689998b4df383c5e33955ceb6bf84d8a884c74904d6a

325fe657b808ef82a1b298af1542fc6f885204952372345b2f93725f0f452013

d42920cb02fcba93dae29713be0c3e00b0b63c4d6b54a0370d069cb7c246e957

83c37eb52fcc3b7ddf17333c898e5f3affc8d4ba8c3577bb4534d59745dc0876

bfa0e84e7500c212165e8dbe34c57a3a4a6658840863370e6892242bee752eb9

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

Campaign

RLMA-2024-11083GENERIC-simple-testsRLUA-2026-00493

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks malware-test-pack-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