Packagist Supply Chain Attack Infects 8 Packages with Linux Malware
A new, coordinated supply chain attack has compromised eight packages on Packagist. The attack injects malicious code designed to retrieve and execute a Linux binary hosted on GitHub Releases. This isnβt a typical composer.json compromise; The Hacker News reports that the malicious code was inserted into package.json files, specifically targeting projects that incorporate JavaScript components.
This vector is critical. Attackers are shifting their focus to broader supply chain points beyond traditional package managers. By targeting package.json, they aim for projects that bundle JavaScript, expanding their reach to a different set of development workflows and environments. This shows a clear intent to maximize impact by leveraging the widespread use of JavaScript in modern applications, even if the primary package manager is Composer.
What This Means For You
- If your development pipeline uses Composer and incorporates JavaScript packages, you need to audit your `package.json` files immediately. Check for any unauthorized modifications or suspicious entries that could fetch external binaries. This isn't just about Composer anymore; it's about the entire dependency tree. Assume compromise and validate every external dependency.
π‘οΈ Detection Rules
2 rules Β· 6 SIEM formats2 detection rules auto-generated for this incident, mapped to MITRE ATT&CK. Sigma YAML is free β export to any SIEM format via the Intel Bot.
Traffic to Compromised Vendor β Packagist
Indicators of Compromise
| ID | Type | Indicator |
|---|---|---|
| Packagist-Supply-Chain-Attack-2026-05 | Supply Chain Attack | Packagist packages |
| Packagist-Supply-Chain-Attack-2026-05 | Code Injection | Malicious code inserted into package.json |
| Packagist-Supply-Chain-Attack-2026-05 | Malware | Linux binary retrieved from GitHub Releases URL |