Maze is hiring two satire creators and puts ad money behind the pieces that land, so the Exploit is becoming a real channel. But every Maze ad and logo on the Exploit sends readers to the homepage with only utm_source=theexploit, whatever they just read. A practitioner laughing at "Vulnerability Scanner Now Offers Discounts for Every Finding It Gets Wrong" is one click from Maze's actual claim, that 90% of the vulnerabilities it investigates are not exploitable, and the site never shows it to them. Nor can Maze tell which articles or writers bring demos, which is what decides where the ad money and the 3% writer share should go.
First action
Add a themed "unfunny version" card to the ten most-read Exploit articles.
How to measure it
Exploit-sourced demo requests
- Now
- –
- Target
- 10 a month
- By
- 90 days
Steps
Pick themes
Five Maze themes and the real page for each.
Head of Marketing 1 day
Tag the archive
One theme per article, starting with the most read.
Marketing Coordinator 2 days
Build the card
A small, clearly labelled card below each story.
Web Developer 2 days
Tag the links
utm_campaign by article slug and writer.
Marketing Coordinator 1 day
Match paid
Boosted pieces land on a themed page with a demo form.
Head of Marketing 1 week
Brief writers
Each pitch names its Maze theme, without changing the joke.
Staff Writer (Satire), the Exploit 1 day
Report monthly
Visits, sign-ups and demos by article and writer.
Head of Marketing monthly
Why it works
Tag each Exploit article with one Maze theme (scanner noise, exploitability, remediation ownership, CISO burnout, AI code) and add a small card under the story: "The unfunny version", one sentence and a link to the matching real page (the exploitability post, the Cohere Health story, the remediation page or a vulnerability write-up). Give each link a utm_campaign with the article slug and writer, swap the generic banner for the themed one, and when an article is boosted with paid spend, send the ad to a themed landing page, not the homepage. Report Exploit-sourced visits, newsletter sign-ups and demos by article every month.
The joke has already done the hard part: it got a sceptical practitioner to recognise their own problem. A themed link catches that moment, and per-article tracking turns the Exploit from brand spend into a channel Maze can budget like any other.
Ready to use
CopyExploit "unfunny version" card
THE UNFUNNY VERSION [One sentence of the real problem, e.g. "Most scanner findings are not exploitable in your environment. Maze investigates every one and shows the few that are."] [Read how Maze checks exploitability ->] (link with utm_source=theexploit&utm_medium=article_card&utm_campaign=<slug>-<writer>)
Risks and how to handle them
Selling inside the satire spoils it
Keep the card outside the story and clearly labelled.
Small numbers at first
Judge articles on sign-ups as well as demos.
Evidence
- HiringStaff Writer (Satire), the Exploit (posted November 1, 2026): "the Exploit ... is a satirical publication from Maze"; Maze is hiring "two satire content creators" who each ship "5 articles and 5 videos a month", every story becoming "a short social video, usually a 30- to 90-second news segment". "When one of your pieces performs organically, we often put ad money behind it", and the writer earns "3% of the spend". Writers must have "Real practitioner experience" in security or software.Source
- The Exploittheexploit.co ("Breaking Satire Before Its Patched"; in Maze's menu as "Like the Onion, but for security") has 56 linked articles on its homepage, a newsletter, "Submit Story" and "Advertise". Its Maze ads and "Brought to you by" logo all link to the mazehq.com homepage with only "utm_source=theexploit", whatever the article is about: the piece "Vulnerability Scanner Now Offers Discounts for Every Finding It Gets Wrong" carries the same homepage link as the RSA Conference jokes. Other ad slots rotate parody ads for invented vendors.Source
- Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
- Your blogVulnerability research posts: "PHP2Shell: two critical PHP RCEs, and how to tell if you're affected" (October 22, 2026), "Removed from a Plane project? One invite can bring you back as admin" (October 20), "There's a ten-year-old key confusion bug in PyJWT" (September 16), "Maze Code found a Langfuse SSO bug" (July 2), "Maze Code found an account takeover bug in Saleor" and "79 Gadgets Hidden in a Single Deserialization Flaw". The PHP2Shell post walks readers through a manual "Are you affected?" check; its only Maze calls to action are the site-wide "See Maze investigate a real vulnerability. Book a demo" footer and a newsletter box.Source