Red Hat hit by npm supply‑chain attack - here's how to stay safe
Red Hat has experienced a significant npm supply-chain attack, compromising numerous JavaScript packages. The breach involved credential-stealing malware that targeted secrets within Red Hat's development systems. Security experts are advising users to check their npm packages for vulnerabilities and assume that any installed affected versions may have exposed sensitive credentials.
- ▪Red Hat was the victim of an npm security breach involving credential-stealing malware.
- ▪The attack compromised 96 versions across 32 packages in the @redhat-cloud-services namespace.
- ▪Malicious code was injected via a compromised GitHub account, affecting the build process of Red Hat products.
ZDNet files mainly under tech. We currently carry 486 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
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 | ZDNet |
| Canonical URL | https://www.zdnet.com/article/red-hat-hit-by-npm-supply-chain-attack-how-to-stay-safe/ |
| Publication time | Wed, 03 Jun 2026 15:33:57 GMT |
| Retrieval time | 2026-06-03T15:37:10.746Z |
| Last seen | 2026-06-03T15:37:10.746Z |
| 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 | rd1p1AFxuISx |
| 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
Tech Home Tech Security Red Hat hit by npm supply‑chain attack - here's how to stay safe Days after IBM and Red Hat announced a master security plan for open-source software, Red Hat suffers a major breach of its own. Here's what you can do about it. Written by Steven Vaughan-Nichols, Senior Contributing EditorSenior Contributing Editor June 3, 2026 at 8:33 a.m. PT John Keeble/Getty ImagesFollow ZDNET: Add us as a preferred source on Google. ZDNET's key takeaways Red Hat was the victim of an npm security breach.The company has removed the affected packages.Check whether you use @redhat-cloud-services npm namespace.The npm repository namespace --the JavaScript runtime environment Node.js package manager -- is infamous for security breaches.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at ZDNet.