artifact-lab-3-package-2b6a4744PyPI
Malicious code in artifact-lab-3-package-2b6a4744 (PyPI) Remove it immediately and rotate any exposed credentials.
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-2b6a4744' @ 0.3.1 (pypi) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind 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-2b6a4744 (6 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-2b6a4744 across your stack and pipelines.
If you installed it — respond
artifact-lab-3-package-2b6a4744 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 artifact-lab-3-package-2b6a4744 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 artifact-lab-3-package-2b6a4744 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
Campaign
References
Credits
- Kamil Mańkowski (kam193)
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks artifact-lab-3-package-2b6a4744-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.