Laravel-Lang Composer packages poisoned via rewritten Git tags
Supply Chain Risk · 14 sources · Updated 5mo ago · First seen May 23, 2026

A supply-chain attack hit the Laravel-Lang ecosystem after attackers rewrote Git tags across laravel-lang/lang, laravel-lang/attributes, laravel-lang/http-statuses, and related repositories, causing 233 tagged package versions to resolve to malicious commits. Researchers said the attacker abused GitHub tags that pointed to forked commits rather than altering the visible upstream code, allowing poisoned releases to spread through Composer and Packagist; one report said roughly 700 GitHub repositories were affected. Packagist removed the malicious versions and temporarily unlisted the impacted packages to stop further installs.
The malicious packages added src/helpers.php through Composer's autoload.files, so code executed automatically when applications loaded vendor/autoload.php in common PHP workflows including Laravel, Symfony, PHPUnit, and CI runners. The payload contacted flipboxstudio.info, dropped follow-on malware, and stole secrets including cloud credentials, CI environment variables, developer tokens, SSH keys, browser passwords, cryptocurrency wallets, VPN data, and Windows-specific credentials before encrypting and exfiltrating the data and deleting artifacts to hinder forensics. Security firms urged organizations that installed affected packages after the compromise to treat those environments as breached, rotate all accessible secrets, inspect composer.lock files, monitor for suspicious outbound traffic, and rebuild compromised systems from known-good images.


