LSN โ€” Local Sovereign Network

๐Ÿ”ด CRITICAL โ€” UK Sanctions Evasion ยท Russian-Iranian Proxy Infrastructure ยท State IP Laundering ยท Offshore Shell Network

๐Ÿ‡ฌ๐Ÿ‡ง๐Ÿ‡ฎ๐Ÿ‡ท TI-2026-022A โ€” "The UK-Iran Corridor" โ€” When a UK Shell Company Routes Iranian State Internet

TI-2026-022A ยท Confidence: HIGH ยท Sources: UK Companies House, RIPE NCC, BGP/RIS, Spamhaus, Honeypot DB, OFAC/UK Sanctions Registry

๐Ÿ”ด 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.

  1. Honeypot sees GCS-AS attack traffic with persistent geo-discrepancy
  2. Threat-intel DB shows Cymru origin RU/IR while abuse/RDAP say BE/DE/US/LV/FR
  3. RIPE identifies AS215540 / GCS-AS under UK LLP Global Connectivity Solutions LLP
  4. Companies House identifies OC450701, formed 19 Jan 2024, with two Seychelles IBC members and PSC Evgeniy Marinko
  5. RIPE identifies sponsoring LIR LLC Internet Tehnologii and shared maintainer control with sister ASN AS207713
  6. RIPE/BGP data shows four IROST 213.176.16-19.0/24 subnets 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.

StepEntityJurisdictionRegistration / ObjectRole in the Chain
1Evgeniy MarinkoRussian-linked / Slavic individualPSC of GCS LLP; 75%+ control; verified 13 Dec 2023Human controller. Pre-verification before incorporation shows design, not accident.
2LS TRADING PARTNERS INCSeychellesIBC 215808; Sound & Vision House, Francis Rachel St, Victoria, MaheOpaque LLP member. Offshore secrecy layer.
3LUPINE LOGISTICS LTDSeychellesIBC 215807; same address, same appointment dateSecond opaque member. Consecutive numbering proves same-day shell fabrication.
4Global Connectivity Solutions LLPUnited KingdomOC450701; 19 Jan 2024; Suite 310, 21 Hill Street, HaverfordwestWestern legitimacy wrapper. The British face of the corridor.
5LLC Internet TehnologiiRussiaRIPE sponsoring org ORG-LT104-RIPE; maintainer INETTECH-MNTRussian LIR sponsor with routing authority over GCS, GIR, IROST child routes, and PROXY6 space.
6AS215540 / GCS-ASOperationally Russian, legally UK-facedAllocated 9 Feb 2024Transit and hosting plane used to originate 237 IPv4 prefixes and route Iranian state blocks.
7IROST / IPMIranParent block 213.176.0.0/17; child /24s moved 16โ€“18 Sep 2025Iranian 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.

IPScoreHitsASNGeo-DiscrepancyHoneypot Activity
141.98.233.848819AS215540 GCS-ASAbuse/RDAP: BE ยท Cymru: RU9 failed SSH sessions on 22 May 2026; no payload delivered; classic auth spray from a โ€œBelgianโ€ IP that routes as Russian.
89.23.108.1348016AS215540 GCS-ASAbuse/RDAP: DE ยท Cymru: RU8 failed sessions on 30 May 2026 using junk credentials; probe-only behavior.
78.153.155.2167919AS215540 GCS-ASAbuse/RDAP: US ยท Cymru: RU9 failed sessions on 22 May 2026; U.S.-registered facade, Russian BGP reality.
62.60.234.1407335AS215540 GCS-ASAbuse/RDAP: LV ยท Cymru: IR17 failed sessions between 21 May and 2 Jun 2026; the first IP that pulled the corridor toward Iran instead of Russia.
45.95.233.887216AS215540 GCS-ASAbuse/RDAP: FR ยท Cymru: RU8 failed sessions from 23 May to 16 Jun 2026; no post-auth activity, persistent low-noise scanning.
213.176.16.22900AS215540 GCS-ASParent allocation: IR ยท child routing object re-registered as NL/GCSNot seen attacking; included because it is Iranian state address space now masked inside GCS routing.
213.176.16.10000AS215540 GCS-ASParent allocation: IR ยท child routing object re-registered as NL/GCSNo honeypot activity observed; evidentiary value is routing provenance, not attack volume.
213.176.18.6501AS215540 GCS-ASParent allocation: IR ยท routed through Russian-sponsored UK corridorSingle 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.

ASNEntityCreatedShared AnchorOperational Significance
AS215540Global Connectivity Solutions LLP9 Feb 2024ORG-LT104-RIPE / INETTECH-MNTMain UK-branded corridor; routes IROST 213.176.16/24, .17/24, .18/24
AS207713Global Internet Solutions LLC (GIR-AS)22 May 2022ORG-LT104-RIPE / INETTECH-MNTPredating 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.

ObjectClaimed IdentityObserved AnchorWhy It Matters
185.88.99.0/24proxy6-net49, country IT, org ORG-PL536-RIPEmnt-routes: INETTECH-MNTItalian label, Russian routing control
proxy6.netCommercial proxy storefrontRussian-language / affiliate-driven serviceConfirms this corridor monetizes anonymity directly
ru-quasar-1-mntShadow maintainer seen on GCS-linked IP clusterAppears across BE/FR/IT/PT nodes in investigation dataIndicates 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

MetricObserved ValueImplication
IPv4 prefixes237Not a boutique ASN; meaningful routed estate
IPv6 prefixes39Built by operators who understand normal network hygiene
IPv4 scale~64,256 IPsMaterial commercial footprint
RPKI validity228 / 237 valid (96%)Professionally engineered routing, not amateur abuse
Traffic20โ€“50 Gbps (PeeringDB)Enough throughput to matter operationally and financially
Transit / path anchorsCogent, GTHost, AlbHost, Cloudity, WorkTitans, GOODTECWestern reachability wrapped around Russian-linked routing control
Russian state path presenceRostelecom AS12389 appears in observed pathsConfirms Russian infrastructural gravity
Moscow visibilityVisible from MSK-IX, avg path ~4.3 hopsOperationally 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

๐Ÿ“Ž 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.

TypeEvidenceReliabilitySource
CorporateGCS LLP incorporation, officers, PSCHIGHUK Companies House โ€” OC450701
RoutingAS215540 / AS207713 sponsorship and path dataHIGHRIPEstat, RIPE WHOIS, BGP HE, PeeringDB
Iran anchorIROST parent/child allocations and routing datesHIGHRIPEstat whois + routing history
Threat telemetryFive attacking GCS IPs + one successful auth from Iranian-routed spaceHIGHLocal Cowrie honeypot / threat_intel DB
Proxy ecosystemPROXY6 block with INETTECH-MNT route authorityHIGHRIPEstat whois for 185.88.99.0/24
Sanctions frameGovernment of Iran public-body definition and service implicationsHIGH / MEDIUMUK Iran Sanctions Regulations 2023; OFAC Iran framework
โš  Personal capacity. Research published independently โ€” not reflecting employer views. Derived from passive observation of attacks against personal infrastructure. Full disclaimer โ†’
โ† Previous Cross-Border Corridors โ€” 1 / 7 Next โ†’