Which versions of random-security-test-pkg are malicious?

The following PyPI versions of random-security-test-pkg are flagged malicious: 1.1.0, 1.1.3. Treat any of these as compromised.

How do I remediate random-security-test-pkg if I installed it?

random-security-test-pkg 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 random-security-test-pkg — how do I know if it already compromised me?

If random-security-test-pkg 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 random-security-test-pkg part of a known attack campaign?

Yes — random-security-test-pkg is associated with the 2024-11-funkymonkeypkg 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 random-security-test-pkg 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 random-security-test-pkg (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging random-security-test-pkg across your stack and pipelines.

Malicious package

random-security-test-pkgPyPI

Malicious code in random-security-test-pkg (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12335

Immediate action

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

pip uninstall random-security-test-pkg

What this malware does

During installation, the obfuscated code attempts to exfiltrate basic information about the host. 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-funkymonkeypkg

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged

1.1.01.1.3

Indicators of compromise (SHA-256)

cc6022d04ac80b0a1294c56d898b7b544ce97e850e783a3ca95478134e170390

8d5e8dadc66c780e3fc3351cf55a305fe623b46a48e96847a7da95ea0e5ec211

ca43b90269074c42155d5d320d840f23ffcb1a553edbc389a2cad521f7f8ffaf

Detection & response playbook

Credential / info stealer

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

Campaign

2024-11-funkymonkeypkg

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks random-security-test-pkg-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