Laravel-Lang Supply Chain Attack
A supply chain attack has compromised the Laravel-Lang repository, rewriting all tags to point to malicious commits. Users running specific Composer commands may inadvertently expose their CI/CD secrets to an attacker-controlled domain. This incident is part of a coordinated campaign affecting multiple Laravel-Lang repositories within a short time frame.
- ▪All tags in the Laravel-Lang repository have been rewritten to point to malicious commits.
- ▪Running 'composer require laravel-lang/http-statuses' or 'composer update' can exfiltrate CI/CD secrets.
- ▪The attack occurred on May 22, 2026, within a 15-minute window.
4 outlets in our directory ran this story, first to last over 43 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/Laravel-Lang/http-statuses/issues/277 |
| Publication time | Sat, 23 May 2026 01:04:53 +0000 |
| Retrieval time | 2026-05-23T01:32:03.762Z |
| Last seen | 2026-05-23T01:32:03.762Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | -8RSVrH0VEEz · 4 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Laravel-Lang / http-statuses Public Uh oh! There was an error while loading. Please reload this page. Notifications You must be signed in to change notification settings Fork 25 Star 28 Code Issues 1 Pull requests 1 Actions Security and quality 0 Insights Additional navigation options Code Issues Pull requests Actions Security and quality Insights {"payload":{"preloaded_records":{},"structured_data":{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Security: All repository tags have been rewritten to point to malicious commits","articleBody":"## Summary\n\nAll tags in this repository have been rewritten to point to malicious commits.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.