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

artifact-lab-3-package-b55680cdPyPI

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

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

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.

The OpenSSF Package Analysis project identified 'artifact-lab-3-package-b55680cd' @ 0.1.1 (pypi) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
0.1.1

Indicators of compromise (SHA-256)

1551be7c93a9149bcaf0349330ef723214923bd2e4eba65930b725144335f8e9
e87f0edb82a994fd382dfba47083df3b7666f11ae2254e88ce414103d9dd0293
be4896eebe0a6b7185d165cec1e593faea8a14a8b2386711ef9c08657273bb31
e8d817638d3140e9cb778fe32c48692f3a8413da8cf718e98eac7a4eaf716097

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-b55680cd (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-b55680cd across your stack and pipelines.

  2. If you installed it — respond

    artifact-lab-3-package-b55680cd 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-b55680cd 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-b55680cd 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-b55680cd 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)
  • OpenSSF: Package Analysis · finder

Detect & block this

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