Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

artifact-lab-3-package-2387cbf7PyPI

Malicious code in artifact-lab-3-package-2387cbf7 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12197
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall artifact-lab-3-package-2387cbf7

What this malware does

Packages showing simple variants of revshell with targets to ngrok. Most probably experiments. Later versions moved to use Burp Collaborator to exfiltrate simple data. Pentest? An artifact from some red team curse?

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-08-lab-artifacts-revshell

Reasons (based on the campaign):

  • The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

  • 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

1 flagged
0.1.1

Indicators of compromise (SHA-256)

27776d2a3af6ace1d44128f9ec8a83b2bf6b9444e938370cf922576484cb16e5
7acac602c6445456648e5d2df157f8b6085f8fb7fa4f001ec1d9fffd97da3294
4ac099efe3fc08e97b89a443bf402d03f44d0ee0b683f885223957ed11b3bd73

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for artifact-lab-3-package-2387cbf7 (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging artifact-lab-3-package-2387cbf7 across your stack and pipelines.

  2. If you installed it — respond

    artifact-lab-3-package-2387cbf7 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.

  3. Did it already run?

    If artifact-lab-3-package-2387cbf7 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.

  4. How O3 protects you

    O3 blocks artifact-lab-3-package-2387cbf7 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. artifact-lab-3-package-2387cbf7 on PyPI has been identified as a malicious package (version 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-08-lab-artifacts-revshell

References

Credits

  • Kamil Mańkowski (kam193)

Detect & block this

O3 blocks artifact-lab-3-package-2387cbf7-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
artifact-lab-3-package-2387cbf7 (PyPI) malicious package — MAL-2024-12197 | O3 Security