Skip to main content
Mallory
← Back to News
package-repository-poisoningvendor-distribution-compromiseloader-delivery-mechanism

Laravel-Lang Packages Poisoned to Deliver Malware

Supply Chain Risk · 9 sources · Updated 5mo ago · First seen May 20, 2026

Laravel-Lang Packages Poisoned to Deliver Malware

Multiple Laravel-Lang packages were reportedly poisoned to distribute malware through the software supply chain, exposing developers and downstream environments that installed the compromised components. The incident affected a widely used localization package ecosystem for Laravel applications, turning trusted dependencies into a delivery mechanism for malicious code and raising concerns about package integrity in developer workflows.

The broader reporting context underscores continued pressure on organizations from software compromise, ransomware, and data theft incidents, but the clearest common event here is the package poisoning campaign targeting Laravel developers. The case highlights the risk that attackers can abuse legitimate repositories and trusted update paths to spread malware, making dependency verification, repository monitoring, and rapid package auditing critical for defenders.

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.

8 events · May 10, 2023 – May 25, 2026
  1. May 25, 20266mo ago

    Radiology Associates of Richmond data breach affects 266,000

    SecurityWeek reported that a data breach at Radiology Associates of Richmond affected 266,000 individuals. This introduces a new victim disclosure and impact figure not previously captured in the timeline.

    266,000 Affected by Data Breach at Radiology Associates of Richmond - SecurityWeek
  2. May 23, 20266mo ago

    Poisoned Laravel-Lang packages used for malware delivery

    SecurityWeek reported that Laravel-Lang packages had been poisoned to deliver malware, indicating a software supply chain compromise affecting those packages. The reference points to public disclosure of the malicious package activity.

  3. May 20, 20266mo ago

    GitHub hack reportedly impacts 3,800 internal repositories

    A SecurityWeek reference indicates GitHub confirmed a hack affecting 3,800 internal repositories. Because the provided content contains no substantive incident details beyond the headline, only the broad confirmation can be captured.

  4. Apr 5, 20243y ago

    Acuity responds to US government data theft claims

    Acuity addressed claims about stolen US government data, stating that hackers obtained older, non-sensitive information. The statement represents the company's public response and characterization of the impact.

  5. Jan 3, 20243y ago

    Xerox confirms data breach at US subsidiary after ransomware attack

    Xerox confirmed that a US subsidiary suffered a data breach following a ransomware attack. This marks the company's official acknowledgment of compromise and resulting data exposure.

  6. Dec 15, 20233y ago

    Kraft Heinz targeted by ransomware group

    SecurityWeek reported that food giant Kraft Heinz had been targeted by a ransomware group. The reference establishes the company as a victim of a ransomware-related incident.

  7. Nov 29, 20233y ago

    Apache ActiveMQ CVE-2023-46604 vulnerability publicly detailed

    Fidelis Security published an overview of Apache ActiveMQ vulnerability CVE-2023-46604, marking public technical discussion of the flaw and its security implications. The reference indicates disclosure and analysis of the vulnerability rather than a specific victim incident.

  8. May 10, 20234y ago

    Dragos says ransomware gang accessed limited data but failed at extortion

    Dragos disclosed that a ransomware group had obtained limited data from the company but that an elaborate extortion attempt did not succeed. The report indicates the incident did not result in the broader impact the attackers sought.

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.