The phenopacket-store-toolkit package version 0.1.7 includes a malicious phenopacket_store_toolkit-setup.pth file that leverages Python's site.py exec() mechanism to execute a Bun runtime-based JavaScript infostealer on every Python startup. This infostealer downloads the Bun runtime from GitHub, executes obfuscated JavaScript that collects a wide range of sensitive information including environment variables, .env files, SSH keys, cloud credentials, and cryptocurrency assets, and exfiltrates this data to an attacker-controlled GitHub repository. The campaign is linked to the Hades/Miasma (Shai-Hulud) threat actor TeamPCP. The malware includes sandbox detection and may attempt destructive actions such as wiping user data if invalid GitHub tokens are found. It also attempts to spread by publishing infected packages using stolen credentials. The campaign uses obfuscation and novel evasion techniques including embedding dangerous content to bypass AI-based security scanners.

This malicious package compromises the confidentiality of sensitive data including environment variables, cloud and package repository credentials, SSH keys, cryptocurrency assets, and password manager data. It enables attackers to exfiltrate this data to a GitHub repository they control. The malware attempts persistence and lateral spread by publishing infected packages using stolen credentials. It may also perform destructive actions such as wiping user data if invalid tokens are detected. This poses a significant risk of credential theft, unauthorized access, and potential data loss for users of the affected package version.

The malicious behavior is present in phenopacket-store-toolkit version 0.1.7. Users should immediately uninstall this version and avoid using it. Since no official patch or fixed version is indicated, remediation involves removing the compromised package and scanning systems for indicators such as the sentinel file /tmp/.bun_ran. Caution is advised during cleanup due to potential destructive payloads. Monitor for suspicious activity related to GitHub token usage and credential exfiltration. Check vendor advisories or PyPI for any updates or official fixes. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.