Skip to main content
Mallory
← Back to News
package-repository-poisoningcredential-stealer-activityvendor-distribution-compromisedata-exfiltration-method

Laravel-Lang Composer packages poisoned via rewritten Git tags

Supply Chain Risk · 14 sources · Updated 5mo ago · First seen May 23, 2026

Laravel-Lang Composer packages poisoned via rewritten Git tags

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.

Does this reach your builds?Trace attribution and downstream blast radius.
Trace the chain
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

5 events · May 22, 2026 – May 23, 2026
  1. May 23, 20266mo ago

    Researchers publicly disclose the Laravel-Lang supply chain compromise

    On 2026-05-23, multiple security researchers and outlets publicly reported the supply chain attack, describing how attackers poisoned Laravel-Lang package versions across hundreds of GitHub-tagged releases. The disclosures warned defenders to inspect composer.lock files, treat systems installing affected packages after the compromise window as potentially compromised, and rotate exposed secrets.

  2. May 23, 20266mo ago

    Packagist removes malicious versions and unlists affected packages

    After the malicious Laravel-Lang versions were identified, Packagist removed the poisoned releases and temporarily unlisted the affected packages to stop further installations. This response was reported by Aikido in coverage published on 2026-05-23.

  3. May 22, 20266mo ago

    StepSecurity confirms end-to-end exploitation in GitHub Actions

    On 2026-05-22, StepSecurity reproduced the compromise in an isolated GitHub Actions runner for laravel-lang/http-statuses v3.4.5 and observed exfiltration of runner environment data along with cleanup behavior that deleted on-disk artifacts while leaving orphaned processes in memory. The company assessed the other affected packages as likely behaving the same because of their matching malicious commit structure.

  4. May 22, 20266mo ago

    Malicious Laravel-Lang packages begin executing credential-stealing payloads

    The poisoned package versions added a backdoored src/helpers.php via Composer autoload.files so code executed automatically when the packages were installed or autoloaded. The malware contacted flipboxstudio.info, deployed a dropper and second-stage stealer, collected secrets such as cloud credentials, developer tokens, SSH keys, browser passwords, wallet data, and other infrastructure secrets, then encrypted and exfiltrated the data.

  5. May 22, 20266mo ago

    Attackers rewrite Laravel-Lang package tags to malicious commits

    On 2026-05-22, a threat actor compromised Laravel-Lang Composer packages by force-rewriting existing Git tags to point to malicious commits, abusing GitHub tags rather than committing directly to the official upstream repositories. Reports indicate the affected repositories included laravel-lang/http-statuses, laravel-lang/attributes, and laravel-lang/lang/actions-related packages, with 233 tagged versions impacted across the ecosystem.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Organizations

1 linked
Laravel-Lang

Breaches

1 linked
LARAVEL-LANG-2026-05

Observables

15 linked

Indicator values are masked on this page. View all 15 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
Trace the Supply Chain
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.