Show HN: Give This Markdown to Your Coding Agent Before Publishing to NPM
The article discusses various techniques used in the past year to conduct attacks on npm packages. It provides insights into potential exploits and offers mitigation strategies for developers. This resource aims to help project maintainers thoroughly review their work before publishing.
- ▪The article covers techniques such as maintainer account takeover and malicious publishing.
- ▪It includes information on lifecycle hook execution and self-replicating npm worms.
- ▪Developers can find mitigation strategies for various attack vectors, including credential harvesting and phishing infrastructure.
2 outlets in our directory ran this story, first to last over 7 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 →
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 | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=48203219 |
| Publication time | Wed, 20 May 2026 04:45:29 +0000 |
| Retrieval time | 2026-05-20T05:04:59.770Z |
| Last seen | 2026-05-20T05:04:59.770Z |
| 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 | X5J517oP3hzA · 2 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
https://npm-supply-chain-attack-techniques.pagey.site/attack...Website: https://npm-supply-chain-attack-techniques.pagey.siteThis covers all techniques used in past 1 year to conduct various attacks on npm packages. Use it to get your project reviewed thoroughly before publishing.Exploits covered with mitigation information:1. Maintainer Account Takeover and Malicious Publish2. Lifecycle Hook Execution3. Self-Replicating npm Worms4. CI/CD Identity Plane Attacks5. Git-Based Dependency Smuggling6. Remote Dynamic Dependencies7. Phishing Infrastructure Hosted Through npm and Package CDNs8. Credential and Secret Harvesting9. Exfiltration and Dead-Drop Channels10. Persistence and Anti-Forensics11. Obfuscation and Payload Packaging12. Package Naming and Discovery Abuse
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.