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

artifact-lab-3-package-1b4d0db5PyPI

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

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

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

5 flagged
0.2.00.2.20.2.30.2.40.3.0

Indicators of compromise (SHA-256)

be2a733cbd9431a8c4e51e410214890f7c2bb707f9d0423fa60e40ec8cf9af7c
83985ca753144131ccc8e470c2c191dc795a54018f39ad92f28855725febfe25
4888901b5300fab8083b85a88bab6bf9a7560fd36a1877c2f973d234a0b0ddde
83da5ea9dc3931ca7d20d8466fe3ce3b410ba537fd852a60ae781bc1971a0199

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-1b4d0db5 (5 malicious versions). 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-1b4d0db5 across your stack and pipelines.

  2. If you installed it — respond

    artifact-lab-3-package-1b4d0db5 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-1b4d0db5 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-1b4d0db5 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-1b4d0db5 on PyPI has been identified as a malicious package (versions 0.2.0, 0.2.2, 0.2.3, 0.2.4, 0.3.0 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-1b4d0db5-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

artifact-lab-3-package-1b4d0db5 (PyPI) malicious package — MAL-2024-12194 | O3 Security