๐ฌ๐ง๐ฎ๐ท TI-2026-022A โ "The UK-Iran Corridor" โ When a UK Shell Company Routes Iranian State Internet
๐ด Executive Summary
This investigation started where the serious ones start now: not with a leak, not with a subpoena, not with a press release โ with a cheap SSH honeypot in a Romanian apartment that kept attracting the same kind of IP.
The IPs looked European and American in RDAP. Team Cymru kept placing them in Russia. Then some of the same routing fabric touched Iranian state space. Then RIPE pointed to a British LLP. Then Companies House showed that the โBritishโ company was owned through two Seychelles shells with consecutive registration numbers. Then the Russian sponsor appeared. Then the Iranian endpoint resolved to IROST โ the Institute for Research in Fundamental Sciences, operator of .ir, directed by Mohammad-Javad Larijani, a foreign-policy adviser to Ali Khamenei.
- Honeypot sees GCS-AS attack traffic with persistent geo-discrepancy
- Threat-intel DB shows Cymru origin RU/IR while abuse/RDAP say BE/DE/US/LV/FR
- RIPE identifies AS215540 / GCS-AS under UK LLP Global Connectivity Solutions LLP
- Companies House identifies OC450701, formed 19 Jan 2024, with two Seychelles IBC members and PSC Evgeniy Marinko
- RIPE identifies sponsoring LIR LLC Internet Tehnologii and shared maintainer control with sister ASN AS207713
- RIPE/BGP data shows four IROST
213.176.16-19.0/24subnets shifted into this Russian-UK corridor on 16โ18 Sep 2025
GCS LLP is not a normal British ISP โ it is a UK legal wrapper around Russian-controlled routing that currently carries Iranian state internet and proxy infrastructure behind a Western-facing corporate mask.
Sources: Honeypot threat_intel DB; UK Companies House OC450701; RIPEstat/RIPE WHOIS for AS215540, AS207713, 213.176.16.0/24, 185.88.99.0/24; UK Iran Sanctions Regulations 2023.
๐งญ The Discovery Path
The key signal was never the volume. It was the contradiction. Five attack IPs in AS215540 hit the honeypot: 141.98.233.84, 89.23.108.134, 78.153.155.216, 62.60.234.140, and 45.95.233.88. AbuseIPDB/RDAP distributed them across Belgium, Germany, the United States, Latvia, and France. Team Cymru kept collapsing them back into the same answer: Russian origin โ except for one critical outlier, 62.60.234.140, which pointed at Iran.
That geo-discrepancy was the parent clue already visible in TI-019M. This dossier follows it deeper. RIPE showed AS215540 was held by a Welsh LLP with no real public operating footprint. Companies House then showed the LLP was not British capital in any meaningful sense: two Seychelles IBCs as members, a Slavic PSC, identity pre-verified by a London ACSP 37 days before incorporation. RIPE then exposed the Russian sponsor. BGP data exposed the Iranian destination.
This is the whole path in one sentence: honeypot attack traffic โ geo-discrepancy โ RIPE ASN โ UK shell โ Russian LIR โ Iranian state IP space.
Sources: threat_intel DB; evidence item โAS215540 Geo-Discrepancy Matrixโ; Companies House overview/officers/PSC pages; RIPEstat AS overview + whois + routing history.
๐๏ธ The Corporate Architecture
The chain is not messy. It is layered. Every layer solves a different problem: ownership opacity, jurisdictional cover, routing authority, and sanctions-distance.
| Step | Entity | Jurisdiction | Registration / Object | Role in the Chain |
|---|---|---|---|---|
| 1 | Evgeniy Marinko | Russian-linked / Slavic individual | PSC of GCS LLP; 75%+ control; verified 13 Dec 2023 | Human controller. Pre-verification before incorporation shows design, not accident. |
| 2 | LS TRADING PARTNERS INC | Seychelles | IBC 215808; Sound & Vision House, Francis Rachel St, Victoria, Mahe | Opaque LLP member. Offshore secrecy layer. |
| 3 | LUPINE LOGISTICS LTD | Seychelles | IBC 215807; same address, same appointment date | Second opaque member. Consecutive numbering proves same-day shell fabrication. |
| 4 | Global Connectivity Solutions LLP | United Kingdom | OC450701; 19 Jan 2024; Suite 310, 21 Hill Street, Haverfordwest | Western legitimacy wrapper. The British face of the corridor. |
| 5 | LLC Internet Tehnologii | Russia | RIPE sponsoring org ORG-LT104-RIPE; maintainer INETTECH-MNT | Russian LIR sponsor with routing authority over GCS, GIR, IROST child routes, and PROXY6 space. |
| 6 | AS215540 / GCS-AS | Operationally Russian, legally UK-faced | Allocated 9 Feb 2024 | Transit and hosting plane used to originate 237 IPv4 prefixes and route Iranian state blocks. |
| 7 | IROST / IPM | Iran | Parent block 213.176.0.0/17; child /24s moved 16โ18 Sep 2025 | Iranian public-body destination whose internet space is being carried through the corridor. |
This is not diversification โ it is compartmentalization. Seychelles hides the owners, Britain launders the appearance, Russia controls the routing, Iran supplies the state endpoint.
Sources: Companies House OC450701 / officers / PSC; RIPE whois AS215540, AS207713, 213.176.16.0/24; report sections 1โ3.
๐ The IP Census โ All 8 Infrastructure IPs
These are the eight infrastructure points carried into the investigation record. Five attacked the honeypot directly. Three are Iranian-route assets that matter because they show where the corridor terminates.
| IP | Score | Hits | ASN | Geo-Discrepancy | Honeypot Activity |
|---|---|---|---|---|---|
141.98.233.84 | 88 | 19 | AS215540 GCS-AS | Abuse/RDAP: BE ยท Cymru: RU | 9 failed SSH sessions on 22 May 2026; no payload delivered; classic auth spray from a โBelgianโ IP that routes as Russian. |
89.23.108.134 | 80 | 16 | AS215540 GCS-AS | Abuse/RDAP: DE ยท Cymru: RU | 8 failed sessions on 30 May 2026 using junk credentials; probe-only behavior. |
78.153.155.216 | 79 | 19 | AS215540 GCS-AS | Abuse/RDAP: US ยท Cymru: RU | 9 failed sessions on 22 May 2026; U.S.-registered facade, Russian BGP reality. |
62.60.234.140 | 73 | 35 | AS215540 GCS-AS | Abuse/RDAP: LV ยท Cymru: IR | 17 failed sessions between 21 May and 2 Jun 2026; the first IP that pulled the corridor toward Iran instead of Russia. |
45.95.233.88 | 72 | 16 | AS215540 GCS-AS | Abuse/RDAP: FR ยท Cymru: RU | 8 failed sessions from 23 May to 16 Jun 2026; no post-auth activity, persistent low-noise scanning. |
213.176.16.229 | 0 | 0 | AS215540 GCS-AS | Parent allocation: IR ยท child routing object re-registered as NL/GCS | Not seen attacking; included because it is Iranian state address space now masked inside GCS routing. |
213.176.16.100 | 0 | 0 | AS215540 GCS-AS | Parent allocation: IR ยท child routing object re-registered as NL/GCS | No honeypot activity observed; evidentiary value is routing provenance, not attack volume. |
213.176.18.65 | 0 | 1 | AS215540 GCS-AS | Parent allocation: IR ยท routed through Russian-sponsored UK corridor | Single successful login on 4 Apr 2026 using admin:admin; no follow-on commands captured, but success alone matters. |
Structured investigation data records all eight. Direct honeypot telemetry confirms five aggressive scanner nodes plus one successful auth event on Iranian-routed space.
Sources: threat_intel DB (ips, honeypot_sessions); investigation infrastructure records; evidence item โAS215540 Geo-Discrepancy Matrixโ.
๐ฎ๐ท The Iranian Connection
IROST โ the Institute for Research in Fundamental Sciences, formerly IPM โ is not a random university tenant. It is a public Iranian research institute, Iranโs first internet organization, and the operator of the .ir country-code registry. Its director, Mohammad-Javad Larijani, is not a neutral academic administrator. He is a regime insider: adviser to Khamenei on foreign policy, former secretary of Iranโs High Council for Human Rights, and brother of former Chief Justice Sadegh Larijani.
The parent block 213.176.0.0/17 remains clearly anchored in RIPE as IR-IROST-19991208, country IR, org ORG-IROf1-RIPE. Then, on 16โ18 September 2025, four child /24s โ 213.176.16.0/24, 213.176.17.0/24, 213.176.18.0/24, 213.176.19.0/24 โ were shifted into GCS/GIR routing in a coordinated operation.
The child object for 213.176.16.0/24 is the giveaway: netname GCS_SER-NET, country NL, org ORG-GCSL7-RIPE. The parent still says Iran. The child now says Netherlands/GCS. That is not ordinary housekeeping. It is state IP laundering through registry metadata.
This is not โinternational hostingโ โ it is Iranian state address space being made to look Dutch while being carried by a UK shell under Russian sponsorship.
Sources: RIPEstat whois for 213.176.0.0/17, 213.176.16.0/24, 213.176.16.0/22; Wikipedia/IPM and Mohammad-Javad Larijani entries; report section 3.
๐งฌ The Dual-ASN Ecosystem
GCS is not alone. It has a sister organism: AS207713 / GIR-AS, held by GLOBAL INTERNET SOLUTIONS LLC, created in May 2022 โ nearly two years before GCS existed. Both are sponsored by the same Russian LIR, ORG-LT104-RIPE / LLC Internet Tehnologii. Both sit under the same routing authority. Both touch IROST space.
| ASN | Entity | Created | Shared Anchor | Operational Significance |
|---|---|---|---|---|
| AS215540 | Global Connectivity Solutions LLP | 9 Feb 2024 | ORG-LT104-RIPE / INETTECH-MNT | Main UK-branded corridor; routes IROST 213.176.16/24, .17/24, .18/24 |
| AS207713 | Global Internet Solutions LLC (GIR-AS) | 22 May 2022 | ORG-LT104-RIPE / INETTECH-MNT | Predating backbone; routes IROST 213.176.19/24; customers include Melbikomas UAB and SmartApe LLC |
Melbikomas and SmartApe matter because they are not prestige enterprise tenants. They are names that recur in the bulletproof and low-abuse hosting ecosystem. Add that to the shared Russian sponsor, the shared Iranian routing, and the split-AS design, and the picture sharpens: one ASN for scale, one ASN for compartmentalization, both under the same hand.
This is not redundancy for resilience โ it is redundancy for deniability.
Sources: RIPEstat whois for AS215540 and AS207713; evidence item โSister ASN AS207713 (GIR-AS)โ; finding โDual-ASN Ecosystemโ.
๐ถ๏ธ The PROXY6 Shadow
One more structure hangs off the same corridor: PROXY6 LLC, a commercial proxy service at proxy6.net that openly markets proxies and an affiliate program. Its block 185.88.99.0/24 is registered in RIPE with country IT โ Italy โ yet the routing authority on the block is INETTECH-MNT, the same Russian maintainer that powers GCS and GIR.
| Object | Claimed Identity | Observed Anchor | Why It Matters |
|---|---|---|---|
185.88.99.0/24 | proxy6-net49, country IT, org ORG-PL536-RIPE | mnt-routes: INETTECH-MNT | Italian label, Russian routing control |
proxy6.net | Commercial proxy storefront | Russian-language / affiliate-driven service | Confirms this corridor monetizes anonymity directly |
ru-quasar-1-mnt | Shadow maintainer seen on GCS-linked IP cluster | Appears across BE/FR/IT/PT nodes in investigation data | Indicates a second Russian operational hand inside the same perimeter |
The current RIPE fetch confirms INETTECH-MNT control over PROXY6 with high confidence. The ru-quasar-1-mnt link sits at medium confidence: it was confirmed in the investigation data and earlier cluster evidence, but not on the main AS215540 aut-num object. That uncertainty does not weaken the PROXY6 point. It narrows it: the Russian routing sponsor is confirmed; the secondary shadow maintainer is highly plausible and probably role-specific.
PROXY6 is not adjacent noise โ it is what the corridor looks like when sold as a product.
Sources: RIPEstat whois for 185.88.99.0/24; evidence items โPROXY6 LLC IP Blockโ and โru-quasar-1-mnt Maintainer Clusterโ; report section 4.
โ๏ธ The Sanctions Question
The legal question is simpler than the networking question. UK Iran sanctions regulations define the โGovernment of Iranโ to include its public bodies and agencies. IROST is a public body. It operates critical national internet functions. GCS LLP is a UK LLP. That gives UK jurisdiction.
The regulations do not need to say โBGPโ to be relevant. Internet transit is not metaphysical. It is a service. It has commercial value. It enables the beneficiary to operate. If a UK LLP is routing address space for an Iranian public body without a licence, the sanctions question is not theatrical. It is live.
The U.S. angle is just as uncomfortable. Most observed AS paths for GCS traverse Cogent (AS174), a U.S. Tier-1. If GCS is carrying Iranian state space and Cogent is carrying GCS, then U.S. transit is part of the corridor whether Cogent intended that or not.
This is not a passive peering curiosity โ it is a commercial service chain touching a sanctioned state environment through a British shell and a Russian routing sponsor.
Sources: UK Iran (Sanctions) Regulations 2023, Reg. 2 and related provisions; RIPEstat BGP state; report section 7; evidence item โUK Iran Sanctions 2023 โ Applicability to IROST Routingโ.
๐ก BGP Analysis
| Metric | Observed Value | Implication |
|---|---|---|
| IPv4 prefixes | 237 | Not a boutique ASN; meaningful routed estate |
| IPv6 prefixes | 39 | Built by operators who understand normal network hygiene |
| IPv4 scale | ~64,256 IPs | Material commercial footprint |
| RPKI validity | 228 / 237 valid (96%) | Professionally engineered routing, not amateur abuse |
| Traffic | 20โ50 Gbps (PeeringDB) | Enough throughput to matter operationally and financially |
| Transit / path anchors | Cogent, GTHost, AlbHost, Cloudity, WorkTitans, GOODTEC | Western reachability wrapped around Russian-linked routing control |
| Russian state path presence | Rostelecom AS12389 appears in observed paths | Confirms Russian infrastructural gravity |
| Moscow visibility | Visible from MSK-IX, avg path ~4.3 hops | Operationally Russian even when the paperwork says UK/NL |
Rapid growth matters too. AS215540 went from allocation on 9 Feb 2024 to first observed routing on 8 Oct 2024 to 237 IPv4 prefixes by 17 Jun 2026. That is not organic artisanal growth. That looks like pre-existing customers being migrated into a new legal shell.
This is not a shell with no infrastructure โ it is a shell with a real backbone behind it.
Sources: bgp.he.net/AS215540; PeeringDB net API for ASN 215540; RIPEstat BGP state and path-length data; report section 5.
๐๏ธ The Seychelles Pattern
The Seychelles members are not decorative. They are the opacity mechanism. LUPINE LOGISTICS LTD and LS TRADING PARTNERS INC sit at the same Sound & Vision House address in Victoria, Mahe. Their registration numbers โ 215807 and 215808 โ are consecutive. That means they were created together, almost certainly by the same formation agent, for the same purpose.
There is no evidence of real logistics operations. There is no evidence of real trading operations. There is evidence of synchronized shell formation feeding directly into a UK LLP that later routes Iranian state space. That is enough.
This is the same offshore grammar seen elsewhere in the dossier corpus: use a reputable-facing jurisdiction for the public wrapper, use a secrecy jurisdiction for the members, and keep the real operator one layer further back. It is not business structuring โ it is ownership laundering. The broader Seychelles shell pattern will be revisited in TI-2026-024.
Sources: Companies House officers page for OC450701; investigation actor records for LS TRADING PARTNERS INC and LUPINE LOGISTICS LTD; report section 1.2.
โ Conspiratorial Questions
โ What if GCS is an intelligence front?
There is no direct evidence in this dossier proving an intelligence-service owner. There is direct evidence of a structure optimized for concealment: pre-verified PSC, offshore members, Russian routing control, Iranian state traffic, and false country presentation in RIPE child objects. If this is not an intelligence front, it is at minimum an infrastructure platform whose design choices are indistinguishable from one.
โ What if the IROST routing is deliberate state-level operations rather than commodity hosting?
The timing argues for deliberation. Four IROST /24s moved on 16โ18 Sep 2025 in a coordinated block, not over months. The child objects were rewritten to point at GCS and, in at least one case, to country NL. That is not what accidental tenancy looks like. That is what purposeful re-homing looks like.
โ What does โconnectivity solutionsโ really mean when you solve connectivity for sanctioned entities?
It means the bland language is doing work. โConnectivity solutionsโ sounds neutral until you trace the beneficiary. Then the phrase stops being technical and becomes evidentiary: who is being connected, through which legal mask, under whose routing authority, and why was the original country scrubbed from the child object?
โ Why verify Marinkoโs identity 37 days before the LLP existed?
Because this structure was assembled in advance. The PSC, the shell members, the UK wrapper, and the routing sponsor did not meet by chance. This company was born as a vehicle, not as a business that later became opaque.
๐๏ธ Read Between the Lines
โก What this report is not saying outright โ but the evidence says for us:
- The UK company is the least important part of the structure. Britain is the costume. Russia is the routing authority. Iran is the state beneficiary. Seychelles is the fog machine.
- The geo-discrepancy is not a bug โ it is the operating model. When five attacking IPs present as BE/DE/US/LV/FR while routing as RU/IR, jurisdictional confusion is the product.
- The Iranian child objects were rewritten because someone needed machines to mis-see them. Humans can still inspect the parent IROST block. Automated systems often stop at the child.
- One apartment honeypot found the corridor from the abuse edge inward. Imagine what a national CERT or Tier-1 with full telemetry already knows and has not yet published.
- If Cogent, GTHost, or other Western transit providers did not know what they were carrying, this dossier tells them now. If they did know, the silence becomes part of the story.
- This is the kind of infrastructure that becomes visible only when you correlate attack telemetry, registry records, and corporate filings together. Each source alone looks deniable. The graph does not.
๐งช Methodology
How this was discovered: A single Cowrie SSH honeypot flagged repeated attack traffic from GCS-AS infrastructure. An AI-assisted enrichment pipeline then resolved each IP across AbuseIPDB, Team Cymru, RIPE/RDAP, Shodan-class enrichment, and the local entity-link graph. Geo-discrepancy became the trigger condition. RIPE WHOIS, BGP state, Companies House, and sanctions sources then turned a scanner cluster into a state-infrastructure corridor.
- Passive collection: Cowrie sessions, credentials, successful auths, command/download traces
- Multi-source enrichment: AbuseIPDB, Team Cymru, RDAP/RIPE WHOIS, GreyNoise, Shodan-class metadata, BGP/RIS context
- Entity-linking: IP-to-ASN, IP-to-maintainer, IP-to-corporate-record, and IP-to-sanctions-context correlation
- Institutional anchoring: UK Companies House, RIPE org objects, PeeringDB, BGP toolkit data, UK legislation
- Human editorial control: AI found the corridor; human review kept the claims inside the evidence
No unauthorized access was performed. Everything in this dossier comes from passive honeypot telemetry or public records.
๐ Linked Dossiers
- TI-019M โ the geo-discrepancy parent map that first exposed GCS-AS as a Russian-shaped network wearing Western addresses
- TI-020A โCartographers of Nowhereโ โ why country disagreement across routing, abuse, and registration is a first-class forensic signal
- TI-2026-024 โ forthcoming Seychelles-shell pattern analysis that generalizes the consecutive-IBC tactic seen here
๐ Sources & Evidence Chain
Machine-readable evidence exists in the dossier pipeline for TI-2026-022: actor records, findings, infrastructure, connections, and evidence items were cross-checked against the full OSINT research report before composition.
| Type | Evidence | Reliability | Source |
|---|---|---|---|
| Corporate | GCS LLP incorporation, officers, PSC | HIGH | UK Companies House โ OC450701 |
| Routing | AS215540 / AS207713 sponsorship and path data | HIGH | RIPEstat, RIPE WHOIS, BGP HE, PeeringDB |
| Iran anchor | IROST parent/child allocations and routing dates | HIGH | RIPEstat whois + routing history |
| Threat telemetry | Five attacking GCS IPs + one successful auth from Iranian-routed space | HIGH | Local Cowrie honeypot / threat_intel DB |
| Proxy ecosystem | PROXY6 block with INETTECH-MNT route authority | HIGH | RIPEstat whois for 185.88.99.0/24 |
| Sanctions frame | Government of Iran public-body definition and service implications | HIGH / MEDIUM | UK Iran Sanctions Regulations 2023; OFAC Iran framework |