This Week in Security: What’s in a name, the AI Bugpocalypse Hits Everyone, OpenWRT flaws, and Duress Passwords
The article discusses recent developments in cybersecurity naming conventions, vulnerability disclosures, and patch management practices. It highlights a critical OpenWRT DHCP vulnerability that has been patched, Cisco's shift away from assigning CVEs to many bugs, and Microsoft's recommendation for a three‑day patch window. The piece also notes the proliferation of naming schemes for threat groups, including new classifications introduced by Google.
- ▪Google has added new threat‑group naming categories such as RELIC, CASTLE, and COMET alongside existing schemes from CrowdStrike and Microsoft.
- ▪A stack‑based buffer overflow bug in OpenWRT's DHCP server was fixed, but many legacy devices may remain unpatched.
- ▪Cisco will adopt a twice‑monthly patch cycle and will no longer assign CVEs to most bugs, citing the rapid increase in AI‑discovered vulnerabilities.
- ▪Microsoft is urging organizations to apply patches within three days, a more aggressive timeline than typical patch cycles.
Hackaday files mainly under tech. We currently carry 224 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 | Hackaday |
| Canonical URL | https://hackaday.com/2026/07/31/this-week-in-security-whats-in-a-name-the-ai-bugpocalypse-hits-everyone-openwrt-flaws-and-duress-passwords/ |
| Publication time | Fri, 31 Jul 2026 14:00:37 +0000 |
| Retrieval time | 2026-07-31T14:23:02.758Z |
| Last seen | 2026-07-31T14:23:02.758Z |
| 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 | lORHjEj3oENY · 1 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
This Week In Security: What’s In A Name, The AI Bugpocalypse Hits Everyone, OpenWRT Flaws, And Duress Passwords No comments by: Mike Kershaw July 31, 2026 Title: Copy Short Link: Copy The great thing about standards is there’s so many to pick from, right?. (Insert obligatory XKCD #927 here.) Several companies have developed naming schemes to refer to groups of attacks, and now Google has too. Sometimes, malware, ransomware, or exploit groups name themselves: “Shinyhunters”, “LapSus$”, “Cl0p”, “Lockbit”, and so on. For the groups that don’t advertise their presence, identification and naming can be more difficult. Mostly state-run affairs that didn’t want to draw attention to themselves, these Advanced Persistent Threats (APT) groups were originally simply given numbers.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hackaday.
Discussion
0 commentsMore from Hackaday
