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

artifact-lab-3-packagePyPI

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

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

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.2

Indicators of compromise (SHA-256)

809c91504d44a3ce598ab73a97aa2e3e1240f99e181d423df52c4435816060b7
0c18a16c7c21d93a8819aed298f6691835b1a31546ca573eb94ce4265d4fb291
2267696fdb22e1cf79e1298164ce7a55084adb73838c14619949fd1ba2089391

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 (version 0.1.2). 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 across your stack and pipelines.

  2. If you installed it — respond

    artifact-lab-3-package 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 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 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 on PyPI has been identified as a malicious package (version 0.1.2 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-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 (PyPI) malicious package — MAL-2024-12192 | O3 Security