Supply Chain Compromise Affecting Laravel Lang Ecosystem
A supply chain compromise campaign targeting the open-source Laravel Lang project would allow a malicious actor to execute arbitrary code and exfiltrate sensitive data on affected systems.
Description
Technical context and vulnerability details
Laravel Lang is an open-source project offering localization and internationalization packages for Laravel applications, distributed via Packagist, the official Composer package registry for PHP. On May 23, 2026, a supply chain compromise affecting the Laravel-Lang GitHub organization was discovered by the Socket and Aikido teams. Malicious actors manipulated the GitHub tagging system to point legitimate release tags to a malicious fork, introducing a backdoor enabling remote code execution (RCE) into over 700 versions of the laravel-lang/lang, laravel-lang/http-statuses, laravel-lang/attributes, and laravel-lang/actions packages. Compromised versions include a malicious file named src/helpers.php, automatically executed via the autoload.files entry in the composer.json file. The malicious code acts as a cross-platform stealer allowing the exfiltration of sensitive data present on affected systems. The malware targets in particular .env files, SSH keys, CI/CD tokens, cloud identifiers (AWS, Azure, GCP), Kubernetes tokens, GitHub/GitLab/Bitbucket identifiers, as well as various information stored on development workstations and server environments. This compromise would allow a malicious actor to execute arbitrary code remotely and exfiltrate sensitive data from systems using compromised versions of Laravel Lang packages.
Potential Risks & Impact
Potential consequences upon exploitation
- Remote Code Execution;
- Data privacy breach;
- Theft of infrastructure secrets;
- Compromise of system integrity and deployment chain;
Affected systems
Products, components and targeted versions
- The Composer packages laravel-lang/lang, laravel-lang/http-statuses, laravel-lang/attributes and laravel-lang/actions in their compromised versions;
- Any system (developer workstation, CI/CD server, production environment) having executed composer install or composer update integrating one of the affected versions is considered compromised.;
Recommended Remediations & Actions
Immediate actions and recommended mitigations
- Check the composer.lock file to identify the presence of the laravel-lang/lang, laravel-lang/http-statuses, laravel-lang/attributes and laravel-lang/actions packages in their compromised versions and block them until healthy versions are available.;
- Immediately reset all secrets exposed to affected environments;
- Rebuild affected hosts, containers, and CI/CD pipelines from known healthy images;
- Audit outgoing network logs for suspicious connections to flipboxstudio[.]info;
- Block network compromise indicators presented in the corresponding section;
- Preserve logs and artifacts before any cleanup operation: composer.lock, Composer cache, deployment logs, process execution logs, network/DNS logs, cloud and Kubernetes audit logs, contents of temporary directories;
INDICATORS OF COMPROMISE:
- Packages compromis
- laravel-lang/lang
- laravel-lang/http-statuses
- laravel-lang/attributes
- laravel-lang/actions
- (La liste des versions associées est présente au niveau de la première référence)
- Fichier et répertoire malveillants
- src/helpers.php
- sys_get_temp_dir()/.laravel_locale/
- DebugChromium.exe
- Indicateurs réseaux
- flipboxstudio[.]info
- hxxps://flipboxstudio[.]info/payload
- hxxps://flipboxstudio[.]info/exfil
- 169.254.169[.]254
Sources & External Links
Vendor security advisories and documentation
Advisory Specifications
CSIRT Emergency Response
Is your organization affected or do you suspect an incident? Our security experts are available to assist.
Report an incidentGet our alerts by email
Subscribe to receive our security alert bulletins and Iservices news straight to your inbox.