Planted Stories & Leaked Dossiers
A 'whistleblower' leak or exclusive drops and is echoed across outlets, engineered to look organic and feed every other vector.
Summary
Planted stories and leaked dossiers are the seed content of many campaigns — a fabricated or selectively stripped 'whistleblower' document, exclusive, or tip given to a willing outlet, designed to look organic and give every downstream amplifier (social, media, search, AI) something concrete to point at. The seed is engineered so the narrative appears sourced and corroborated even when it traces to a single operator-controlled origin.
How the attack works
- Operators prepare a dossier, document, or 'leak' — real material stripped of context, or fabricated outright.
- It is placed with a sympathetic or undiscerning outlet as an 'exclusive' or 'whistleblower' story.
- The story is amplified across coordinated outlets and social to create apparent corroboration.
- Downstream coverage cites the original 'scoop' rather than independent verification.
- The seed then feeds SEO poisoning, AI poisoning, and lawfare vectors.
Tell-tale signs you're under this attack
- An exclusive or leak appears and is echoed by multiple outlets within 24–48 hours
- Downstream coverage cites the original rather than independent sources
- The 'leak' is selectively missing exculpatory context
- The source is anonymous or newly created
- Coverage aligns with a financing, election, or launch window
First-line defense
Perform provenance analysis on the 'leak' immediately — what was withheld, who had access, what is selectively missing — and publish the missing context as retrievable counter-content before the seed consolidates as 'widely reported.'
The defense playbook
- 1
Analyze the provenance of the leak: what was withheld, who had access, what context is missing.
- 2
Request right-of-reply and factual corrections from the originating outlet and aggregators.
- 3
Publish the missing context as retrievable, authoritative counter-content on owned domains.
- 4
Trace the seed to its operator-controlled origin for attribution and any legal action.
- 5
Prevent the seed from feeding SEO and AI poisoning by correcting the index early.
- 6
Brief journalists with verified context to break the 'others are reporting it' assumption.
Legal & platform options
- Defamation and false-light action against publishers of fabricated or stripped material
- Conversion and trade-secret claims where stolen documents are used
- Right-of-reply and correction requests to publishers
- Platform enforcement for coordinated amplification of the planted story
Recovery outlook
Best disrupted at the seed stage (first 72 hours); once a planted story is 'widely reported,' deindexing and counter-content typically require 2–3 months, with AI answers taking longer to correct.
Facing this pattern right now?
Speed in the first 72 hours is the single biggest determinant of outcome. We triage, attribute, and deploy the matching playbook — confidentially.