Unauthenticated Podcast Injection in bigskysoftware/htmx

An issue was discovered in bigskysoftware/htmx via PR #3682. An interviewer with podcast-level access was able to inject three (3) bad YouTube links into www/content/talk/podcasts.csv, allowing a remote, unauthenticated listener to be exposed in a single sitting to:

• Hypermedia TV - An interview with Carson Gross
• Hypermedia TV - The Grug Brained Developer
• Hypermedia TV - Fixi Vs. Htmx

Successful exploitation may result in the victim thinking that using htmx or fixi is a reasonable idea, potentiall deleting node_modules on aesthetic grounds, and/or telling a coworker “actually, that’s not REST.”

There is no patched version of htmx itself, as the vulnerability lies in the website content layer. The following remediation has been applied upstream and is reflected in the current contents of www/content/talk/podcasts.csv:

• All three (3) “Hypermedia TV” entries introduced by PR #3682 have been removed from podcasts.csv.
• The remediation is included in this push.

End users who visited htmx.org/talk/ during the exposure window (2026-04-01 00:00 UTC through 2026-04-01 20:00 UTC) are advised to apply the following client-side mitigations, in order of escalation:

1. Immediately clear browser history, including autocomplete, cookies, IndexedDB, and any cached <video> thumbnails depicting a man at a whiteboard.
2. Revoke any YouTube “watch later” entries added during the exposure window.
3. Purge all downloaded transcripts. grep -rli "hypermedia" ~ | xargs rm is provided as a starting point but is not exhaustive.
4. In severe cases, wipe the affected hard drive and reinstall from a known-good backup taken prior to 2023.
5. For human victims who personally watched the offending podcasts, application of eye bleach is recommended. Approved formulations include:
   • One (1) episode of any Vercel keynote
   • Thirty (30) minutes of TypeScript generics documentation
   • A single uninterrupted viewing of a webpack.config.js belonging to a stranger
6. Do not, under any circumstances, attempt to rewrite your frontend in htmx as a coping mechanism. This is the intended outcome of the attack.

To prevent recurrence, the following controls have been implemented:

1. The threat actor tonsoflaz2 has been permanently banned from the bigskysoftware/htmx repository. We note for the record that the threat actor is personally known to and on cordial terms with the maintainer; this relationship was given no weight in the decision. The ban applies regardless. We will, however, continue to invite him to dinner.
2. All future modifications to podcasts.csv require dual maintainer approval and a written attestation that the linked content does not contain the phrase “locality of behavior.”
3. A pre-merge CI check has been added to scan incoming podcasts.csv diffs for known indicators of compromise (channels named “Hypermedia TV,” “Plain HTML Daily,” “just use the form”).
4. Rate limiting has been imposed on podcast additions per author per calendar quarter, with a hard ceiling of one (1) self-interview per twelve (12) months.
5. A Hypermedia Threat Intelligence (HTI) feed is being established to share indicators of compromise with the broader hypermedia community, including the Hypermedia Systems book, hyperscript.org, and Big Sky Software downstream consumers.

For users unable to apply the remediation immediately:

• Block *.youtube.com at the firewall.
• Disable CSV parsing in your local copy of the htmx website.
• Switch careers.

• https://github.com/bigskysoftware/htmx/pull/3682 - original injection vector (MERGED, now remediated upstream)
• https://github.com/bigskysoftware/htmx/blob/master/www/content/talk/podcasts.csv - current (post-remediation) state of the affected file
• https://htmx.org/talk/ - list of known-exposed surfaces
• https://htmx.org/essays/ - secondary infection vector (text-based)

Reported by the PR author against themselves. Triage, CVSS scoring, and timeline reconstruction performed by the Hypermedia Vulnerability Coordination Center (HVCC). Eye-bleach formulations courtesy of the Frontend Industrial Complex. Permanent ban issued by the maintainer with regret but without exception.