FBI links SEO poisoning to US$28 million in ransomware payments

- Reading
- 5 min
- Tables
- 1
An FBI alert cited by Barry Schwartz of Search Engine Roundtable points out that SEO poisoning techniques have already generated US$28 million in ransomware payments. For those who handle marketing and search, this means the brand's own ranking has become an attack vector.
No recap semanal da Search Engine Roundtable publicado em 20 de novembro de 2026, Barry Schwartz passou por mais de vinte itens... (placeholder)
In the weekly Search Engine Roundtable recap published on November 20, 2026, Barry Schwartz covered more than twenty items: the status of Google's November core update, new filters in the Search Analytics API, changes to AI Overviews, "web only" tests on Bing and ChatGPT. One of them, however, isn't about ranking: it's about security. According to the FBI alert cited in the video, SEO poisoning techniques have already been linked to US$28 million in ransomware payments.
For those who decide channel budgets and search strategy, this number changes how SEO is read as a discipline. It isn't just about ranking well: it's about making sure no one is ranking poorly in your domain's name, or using the trust Google places in your site to distribute malware.
What the FBI tied to ranking data
SEO poisoning is the name given to the practice of manipulating search results to push malicious pages into top positions, usually exploiting high-volume terms or moments of peak interest (a software launch, a security crisis, a holiday, a sporting event). The user clicks on a result that looks legitimate and lands on a page that installs malware, captures credentials, or opens the door to a broader ransomware attack.
The alert mentioned in the video links this chain to US$28 million in ransoms paid, which suggests that the entry vector, formerly just a click in organic search, is now treated as a corporate-scale risk, not just a brand-reputation nuisance.
How the technique works under the hood
In practice, SEO poisoning rarely depends on a site built from scratch. The most common tactics used by those behind these schemes include:
- Compromising legitimate, poorly maintained sites: an outdated
WordPressinstall, a vulnerable plugin, or an unpatched CMS become hosts for injected spam pages, taking advantage of domain authority that already exists. - Cloaking: the page shows harmless content to Google's crawler and malicious content (or a redirect) to the human visitor, making automatic detection harder.
- Parasite SEO on high-authority domains: PDFs, subfolders, or subdomains hosted on universities, government bodies, or legitimate corporate sites, which Google indexes quickly because it trusts the parent domain.
- Hijacking trending terms: creating hundreds of disposable pages around searches that spike in volume (a popular software name, a newly disclosed security flaw), to capture clicks before legitimate content rises in the ranking.
The common denominator is using the search algorithm's own logic, relevance, authority, freshness, as the mechanism for distributing the scam.
Why this is a growth issue, not just a security one
In short: if your domain is compromised to host poisoning pages, the damage isn't limited to the attacker. It falls on the brand itself, with two effects that matter directly to those who measure search and paid media performance.
The first is algorithmic penalization: Google already treats sites compromised with injected spam as a low-quality signal, which can wipe out positions earned over years of content and authority work. The second is the loss of user trust: once a visitor is redirected to malware from your domain, Google's Safe Browsing can flag the entire site, even for people who never visited the malicious page.
In the same recap, Schwartz mentions that Google Search Console's Search Analytics API gained new filters: brand queries, multimodal, and segmentation by country and device. This update, though announced as an analytics feature, doubles as a monitoring tool: an anomalous spike in brand-query impressions from countries outside your market, or a device-mix jump that doesn't match historical patterns, is usually the first visible sign that something strange has been indexed under your domain.
How to spot poisoning signs on your own site
Detection doesn't require an expensive tool, it requires routine. Some recurring checkpoints:
| Signal | Where to look | What it indicates |
|---|---|---|
| Unknown indexed pages | site:seudominio.com on Google | Content injected without your knowledge |
| Sudden Safe Browsing flag | Google Search Console > Security Issues | Malware or phishing detected |
| Spike in impressions for terms unrelated to the business | Search Analytics API (brand query filter) | Spam pages ranking under your domain |
| New files with no matching deploy | Server logs and file integrity checks | Malicious upload via vulnerable plugin or CMS |
None of these signals alone is definitive proof, but a combination of two or more in the same period usually justifies a full scan.
What to do, and what doesn't work
Switching hosting providers or manually "cleaning" the visible files doesn't solve the problem if the entry-point vulnerability remains open, the attacker comes back through the same outdated plugin or CMS within days. The response that actually reduces risk combines updating all CMS dependencies, auditing users and admin permissions, cross-checking what Google Search Console reports as indexed against what the site actually serves, and, when there's evidence of compromise, requesting a Safe Browsing review only after the fix has been confirmed.
It's worth remembering that this kind of alert, coming from a video recap rather than the FBI's original bulletin, reaches us as second-hand information: useful for understanding the trend, but not a substitute for reading the official notice for those who set corporate security policy.
What remains unclear
The video doesn't detail the period covered by the US$28 million figure, nor does it list the most affected sectors, which limits any direct comparison with the Brazilian scenario. What can already be measured, regardless of the full bulletin, is whether your own domain comes up clean in the checks above, and that can be done today, without waiting for the official report.
Translated from the Brazilian Portuguese original · Read the original
Robots.txt for the AI era: how to configure Google-Extended and Googlebot correctly
A practical guide to auditing the robots.txt of a Brazilian site, separating what each Google crawler does, and understanding why blocking AI training should not, in theory, remove your page from AI Overviews.





