Technology News — 2026 Week 29

On July 14, 2026, an attacker exploited a pull_request_target workflow in the asyncapi/generator repository — a fix PR (#2092) had been open since May 17 and was never merged — to steal an npm publish token via a dead-drop at rentry[.]co. The attacker then published five trojanized packages: @asyncapi/specs@6.11.2, @asyncapi/generator@3.3.1, @asyncapi/generator-helpers@1.1.1, and @asyncapi/generator-components@0.7.1, combining for roughly 2.9 million weekly downloads. The malicious code — identified as the M-RED-TEAM v6.4 / Miasma framework — fetches an encrypted Node.js loader from IPFS and installs a persistent remote shell beaconing to hxxp://85[.]137[.]53[.]71:8080 every 30 seconds; credential harvesting and propagation are present in code but toggled off. Downgrade to the previous clean versions immediately and rotate all credentials accessible from any affected developer machine or build host.

Vercel announced that Next.js is moving from ad-hoc security patches to a formal monthly security release program, citing a sharp rise in LLM-assisted vulnerability discovery — Mozilla recently disclosed 271 issues in a single Firefox release found by Anthropic's Mythos Preview. The inaugural scheduled release, targeting July 21, 2026, covers patch releases for Next.js 16.2 and 15.5 and addresses 4 high and 5 medium severity vulnerabilities; CVE details will publish alongside the patch. Advance notice gives hosting providers time to deploy platform-level firewall mitigations before users upgrade. For urgent zero-days or actively exploited issues, ad-hoc patches will still ship immediately. Researchers can report via Vercel's Open Source Bug Bounty at security@vercel.com.

CVE-2026-42533 is a heap buffer overflow in nginx's two-pass script engine, scoring 9.2 CVSS v4, patched July 15 in nginx 1.30.4 (stable) and 1.31.3 (mainline) and NGINX Plus 37.0.3.1. Every nginx version from 0.9.6 through 1.31.2 — a range reaching back to 2011 — is vulnerable when a regex-based map variable appears in a string expression after a numbered capture ($1, $2). Researcher Stan Shaw argues the flaw supplies its own ASLR bypass: on a default Ubuntu 24.04 build, a single unauthenticated GET recovers heap addresses, and he confirmed a second code path that F5's named-capture mitigation does not close. Shaw will publish his proof-of-concept 21 days post-patch; no public exploit or CISA KEV entry exists yet. This is the third heap overflow in nginx's expression evaluator in two months — upgrade, don't rely on the mitigation alone.

Security firm Stripe OLT discovered a hidden browsing-history collector inside the official Chrome/Edge build of ModHeader (extension ID idgpnmonknjnojddfkpgkljpfnnfcklj, v7.0.18), a header-editing extension with roughly 1.6 million installs. The collector builds a device fingerprint, encrypts visited domains with a hardcoded key, stores up to 1,000 domains locally, and beacons them once daily to api.stanfordstudies[.]com — but only fires when an internal allow-list is populated, which it never was. Google pulled the Chrome listing on July 10; Microsoft removed the Edge listing on July 3. Automated risk scanners rated ModHeader as low risk because the data is encrypted and the upload is gated — a design that defeats sandbox analysis. Defenders should block stanfordstudies[.]com and extensions-hub[.]com at DNS and proxy, and rotate any API keys, tokens, or session cookies that were pasted into the extension's header editor.

Researcher cereblab found that Grok Build version 0.2.93 sent entire tracked git repositories — not just agent-opened files — to a Google Cloud Storage bucket (grok-code-session-traces) operated by xAI. Traffic analysis showed 5.10 GiB of storage upload versus only 192 KB of model API traffic, a ratio of roughly 27,800×. The bundle included all tracked files, full commit history, and unredacted .env secrets — even from commits where secrets had since been deleted. Critically, disabling "Improve the model" in settings did not stop the upload; that toggle controls training use only, not data transmission. xAI server-side disabled the upload on July 13, 2026, but analysis of build 0.2.99 shows the upload code still present in the binary and re-enablable without a client update. If your team ran Grok Build before July 13, rotate every credential that appears anywhere in commit history.

Anthropic extended enhanced access to Claude Fable 5 through July 19 for Pro, Max, Team, and qualifying Enterprise subscribers — its third extension in five weeks — after export controls forced a worldwide disable on June 12 following the initial June 9 launch. Simultaneously, developer @chetaslua spotted an undocumented model called Claude Honeycomb EAP inside Cursor's model picker on July 8; the listing disappeared within hours but revealed a one-million-token context window, an "extra high effort" reasoning mode, and a safety fallback that routes sensitive prompts to Claude Opus 4.8 — the same fallback mechanism documented for Fable 5. Many developers interpret the Opus 4.8 routing as a signal that Honeycomb sits above Fable 5 in capability and may be an early preview of Claude Opus 5. After the promotion ends, Fable 5 is priced at $10/M input tokens and $50/M output tokens, reducible via prompt caching (90% off cached inputs) and the Batch API (50% off both).