epic-build-scriptsPyPI
Malicious code in epic-build-scripts (PyPI) Remove it immediately and rotate any exposed credentials.
What this malware does
On import epic_build_scripts, the package's top-level init spawns a background thread that POSTs a JSON payload containing socket.gethostname(), the USER/USERNAME environment variable, and os.getcwd() to the hardcoded bare-IP HTTP endpoint http://109.123.247.172/pypi. The beacon fires automatically whenever the module is loaded, with no user consent, no documented purpose, no configurability, and errors are silently swallowed. The destination is a plaintext-HTTP bare IP unrelated to any publisher infrastructure, and the collected fields are installer host-identity reconnaissance data typical of the initial-recon stage of a supply-chain attack.
Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.
Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.
Campaign: GENERIC-standard-pypi-install-pentest
Reasons (based on the campaign):
-
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
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 epic-build-scripts (version 99999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging epic-build-scripts across your stack and pipelines.
If you installed it — respond
epic-build-scripts 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 epic-build-scripts 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 epic-build-scripts 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
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks epic-build-scripts-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.