The Double Standard
TI-2026-032H โ The Mirror Thesis: Western Infrastructure Outperforms Chinese Ecosystems in Raw Abuse Output
Executive Summary
After publishing a 10-letter series (031A-J, "The Cloud Silk Road") documenting Chinese cloud infrastructure's role in global SSH attack campaigns, intellectual honesty required turning the same forensic lens on Western providers. The result is unambiguous: 8 Western providers collectively host 1,028 IPs with 525 at abuse_score=100, generating 4,930 honeypot hits across 15 countries. The equivalent Chinese ecosystem โ Tencent, Alibaba, Huawei, Yisu โ accounts for 237 IPs with 174 at abuse=100 and 753 hits.
The Western providers in this series produce 4.3ร the IP volume, 3.0ร the abuse-rated IPs, and 6.5ร the honeypot hits of the Chinese ecosystem documented in 031. The double standard isn't rhetorical. It's mathematical.
The Complete Scorecard
Western Providers โ 032 Series
| Provider | Letter | IPs | Avg Threat | Abuse=100 | Abuse Rate | Hits | Max Threat |
|---|---|---|---|---|---|---|---|
| DigitalOcean | 032D | 350 | 26.1 | 117 | 33.4% | 976 | 100 |
| Google Cloud | 032G | 157 | 32.5 | 77 | 49.0% | 562 | 88 |
| OVH | 032F | 128 | 52.9 | 90 | 70.3% | 1,108 | 100 |
| FranTech/BuyVM | 032E | 121 | 36.3 | 50 | 41.3% | 176 | 90 |
| Contabo | 032F | 91 | 39.8 | 49 | 53.8% | 301 | 95 |
| ColoCrossing | 032A | 74 | 47.4 | 46 | 62.2% | 821 | 99 |
| Psychz+MULTACOM | 032B | 67 | 58.5 | 60 | 89.6% | 440 | 91 |
| SingleHop/Internap | 032C | 40 | 69.7 | 36 | 90.0% | 546 | 95 |
| TOTAL (032) | โ | 1,028 | 38.1 | 525 | 51.1% | 4,930 | 100 |
Chinese Providers โ 031 Series (Comparison)
| Provider | IPs | Avg Threat | Abuse=100 | Abuse Rate | Hits |
|---|---|---|---|---|---|
| Tencent Building (AS132203) | 181 | 53.5 | 156 | 86.2% | 709 |
| Guangzhou Yisu (AS141995) | 18 | 28.0 | 5 | 27.8% | 17 |
| Huawei Cloud (AS55990) | 17 | 6.9 | 1 | 5.9% | 26 |
| Alibaba/Hangzhou (AS37963) | 12 | 40.8 | 8 | 66.7% | 1 |
| Shenzhen Tencent (AS45090) | 9 | 23.8 | 4 | 44.4% | 0 |
| TOTAL (031) | 237 | 46.5 | 174 | 73.4% | 753 |
The Mirror Numbers
The Chinese ecosystem has a higher average threat (46.5 vs 38.1) and a higher abuse rate (73.4% vs 51.1%) โ meaning the Chinese IPs that DO appear are more uniformly malicious. But Western providers produce 4.3ร the volume. In absolute terms: 525 Western IPs at abuse=100 versus 174 Chinese. The West produces three times more maximum-abuse infrastructure. The narrative that Chinese cloud is the primary threat to the global internet is not supported by this data.
The Structural Comparison
Two Architectures of Abuse
The series revealed fundamentally different abuse architectures:
The Chinese Model (031): Concentrated. Tencent's AS132203 alone accounts for 76% of all Chinese IPs. High abuse rate (86.2%) but relatively low volume. State-adjacent companies โ Tencent, Alibaba, Huawei โ with government oversight creating both surveillance capability and, paradoxically, somewhat better abuse control (Huawei at 5.9% abuse rate). The threat is strategic: when abuse happens, it may be state-tolerated or state-directed.
The Western Model (032): Distributed. No single provider dominates โ DigitalOcean leads by volume (350 IPs) but OVH leads by hits (1,108). The abuse rate varies wildly: from 33.4% (DigitalOcean) to 90% (SingleHop). Eight providers across US, France, Germany, Canada operate independently with no coordinating oversight. The threat is systemic: it's the absence of coordination, the gap between providers, the overlapping jurisdictions that create the attack surface.
Five Patterns Across Seven Letters
Pattern 1: The Distance Gradient
Consistently across every provider examined, abuse intensity increases with organizational and geographic distance from headquarters:
- OVH: France avg 48.7, Canada 60.7, Poland 63.1
- Contabo: Germany avg 13.6, France avg 52.9 (4ร differential)
- Google Cloud: US avg 19.6, Belgium avg 44.9 (2.3ร differential)
- DigitalOcean: US avg 17.0, India/Singapore 2ร US rate
- OVH founder Octave Klaba's personal IPs: avg 6.7 (clean)
The closer you are to the people who set the policies, the better the enforcement. This is universal across corporate structures, countries, and regulatory frameworks.
Pattern 2: The Acquisition Decay
Every provider with a private equity or acquisition history shows elevated abuse:
- ColoCrossing โ HostPapa acquisition: 62.2% abuse rate, Spamhaus-listed
- SingleHop โ INAP โ Internap Holding LLC: 90% abuse rate, twice-bankrupt, highest avg threat in series (69.7)
- Psychz โ Brander Group affiliation: 89.6% abuse rate, RIPE-NCC-HM-MNT on a US provider
When infrastructure changes hands, the compliance team is the first casualty. Abuse policies written by the founder don't survive the first PE fund manager.
Pattern 3: The Campaign Ecosystem
The hassh-14b2ddda386a4d10 botnet (628 IPs, 48 countries, libssh2_1.11.0) appears on every Western provider in this series:
| Provider | Nodes | Rank in Botnet |
|---|---|---|
| OVH | ~45 | LARGEST host |
| Psychz Networks | ~34 | 2nd |
| ColoCrossing | ~33 | 3rd |
| SingleHop/Internap | ~20 | 4th |
| FranTech/BuyVM | 14 | 5th |
| DigitalOcean | ~8 | 6th |
| Contabo | ~4 | 7th |
A single botnet draws hosting from all seven providers simultaneously. No one provider can stop it because the campaign exists across all of them. Contabo has its own exclusive campaign (hassh-16443846184eafde) that also cross-contaminated to Google Cloud. The botnets are multi-provider by design.
Pattern 4: The Regulatory Void
Neither US, EU, nor any other regulatory framework addresses hosting abuse as outbound attack infrastructure:
- US: Section 230 protects platforms from liability for user content. No equivalent framework for outbound attacks from user infrastructure.
- EU: GDPR addresses data protection. DSA addresses illegal content. NIS2 addresses critical infrastructure cybersecurity. None address the obligation to prevent VPS infrastructure from being used as SSH brute-force platforms.
- Self-regulation: Abuse desks are cost centers, not profit centers. Response time varies from hours (DigitalOcean) to "an empty void" (FranTech).
The regulatory hole is hosting-shaped: every framework addresses what's on a server (content, data, services) but not what the server does to other servers.
Pattern 5: The Hyperscaler Paradox
The two largest companies in this series โ DigitalOcean ($DOCN, NYSE) and Google ($2T market cap) โ contribute the most IPs but the lowest per-IP threat:
| Provider | IPs | Avg Threat | Revenue | Abuse Team |
|---|---|---|---|---|
| DigitalOcean | 350 | 26.1 | $700M+ | Dedicated |
| Google Cloud | 157 | 32.5 | $300B+ | TAG, Mandiant, VirusTotal |
| SingleHop/Internap | 40 | 69.7 | Bankrupt | Unclear |
| Psychz+MULTACOM | 67 | 58.5 | Private | Minimal |
Scale produces lower per-IP density but massively higher absolute abuse volume. The hyperscaler model: abuse at scale is a rounding error on the revenue line, which means it's never truly urgent.
The Mirror Thesis: Proved
What "The American Mirror" Demonstrates
After 031 (The Cloud Silk Road), the natural assumption was that Chinese infrastructure represents a unique threat โ state-adjacent companies tolerating abuse for strategic reasons. This series set out to test whether Western providers were different.
They're not different. They're worse.
- More IPs: 1,028 vs 237 (4.3ร)
- More max-abuse IPs: 525 vs 174 (3.0ร)
- More attacks: 4,930 hits vs 753 (6.5ร)
- More countries affected: 15 vs 4
- More campaigns: dozens vs single-digit
The difference is narrative, not technical. When Tencent hosts attack infrastructure, it's "Chinese cyber aggression." When OVH hosts more attack infrastructure, it's "a customer issue." When Google's Belgian data center runs five simultaneous botnet campaigns, it's "compromised instances." The infrastructure is the same. The botnets are the same. The SSH brute-force is the same. Only the geopolitical framing changes.
Conspiratorial Questions
The Questions Nobody Asks
Q: Why does the cybersecurity industry focus on Chinese and Russian threats while Western infrastructure produces more abuse?
A: Follow the money. The cybersecurity industry is a $200B+ market dominated by Western companies selling to Western clients. The threat narrative โ "Chinese APTs, Russian ransomware" โ drives purchasing decisions. Nobody buys a $50M security platform to protect against attacks originating from DigitalOcean or Google Cloud. The industry needs an external threat to justify internal spending. The data showing that the call is coming from inside the house is bad for business.
Q: Is the regulatory void around hosting abuse intentional?
A: Consider who benefits. The cloud industry generates $600B+ annually. AWS, Azure, GCP together control >65% of the global market. These companies have extensive lobbying operations in Washington, Brussels, and London. A regulation requiring hosting providers to prevent outbound abuse would impose costs on every cloud provider. The regulatory void isn't an oversight โ it's a feature of regulatory capture by the cloud industry itself.
Q: Do Western providers know they host more abuse than Chinese ones?
A: Google literally publishes papers about it (GCAT Threat Horizons). DigitalOcean has a dedicated Trust & Safety team. OVH has a published AUP. They all know. The question isn't knowledge โ it's incentive. A compromised VM running a botnet was a paying customer until it got caught. The economic model incentivizes a detection latency just long enough to capture revenue from the attack lifecycle before terminating the instance. Too fast kills revenue. Too slow creates liability. The sweet spot is the gap between "we're working on it" and "we've terminated the account."
Q: What does it mean that the same botnet (hassh-14b2ddda386a4d10) operates across all seven providers?
A: It means the internet's attack infrastructure is provider-agnostic. The botnet operator doesn't care whether the node runs on a $5 DigitalOcean droplet, a โฌ4.99 Contabo VPS, or a Google Cloud instance. They provision where provisioning is easiest. The botnet's distribution across all seven providers is itself a finding: there is no safe provider. The differences between providers are marketing. The shared attack surface is reality.
Q: Does the West hold China to standards it doesn't apply to itself?
A: Yes. The data is unequivocal. 1,028 Western IPs vs 237 Chinese. 525 Western abuse=100 vs 174 Chinese. 4,930 Western hits vs 753 Chinese. When we published 031 documenting Chinese cloud abuse, the numbers were concerning. Now that we've documented Western providers using the same methodology, the same tools, and the same database โ the numbers are worse. The mirror shows the face you didn't want to see.
Series Methodology
How This Series Was Produced
Every finding in this 8-letter series is derived from the same methodological framework:
- Data source: LSN Threat Intelligence Database โ 8,000+ IPs with multi-source enrichment (Shodan, GreyNoise, AbuseIPDB, RDAP, Cymru, OTX, DShield, Censys, VirusTotal, Pulsedive, IPInfo)
- Campaign detection: HASSH fingerprint clustering + behavioral correlation โ automated detection of coordinated attack groups
- Honeypot: Cowrie SSH/Telnet honeypot providing session data, credentials, commands, and downloads
- Cross-referencing: 30+ prior dossier investigations vectorized and searchable. Every new letter queries all existing data.
- OSINT: Corporate registries (SEC EDGAR, Companies House, Handelsregister), PeeringDB, ARIN/RIPE RDAP, Spamhaus, news archives
- Independence: All 032 letters use identical methodology to 031. Provider selection based solely on IP count in threat database, not preconceived narrative.
The same telescope, pointed in a different direction, reveals the same stars.