๐ TI-2026-023C โ The Virtual Country: How M247's Geofeed Creates Imaginary Geography for Sanctioned Nations
Executive Summary
M247 Europe SRL publishes an official geofeed file at geoip.m247.ro/geofeeds.csv โ an RFC 8805 mechanism that instructs GeoIP databases where their IP addresses "are." This file contains 2,191 entries spanning 116 countries. Among them: Iran, Cuba, Belarus, Russia, Turkmenistan, Zimbabwe, and Congo DRC.
The RIPE database explicitly names these registrations: "M247-Iran" with entity "M247 Ltd Iran" and "M247-Ltd-Cuba" โ a Romanian company with no physical infrastructure in either country, officially instructing the internet's geolocation databases to classify its European servers as Iranian and Cuban endpoints.
This is not a technical curiosity. It is the architecture of imaginary geography โ the mechanism by which a server in Bucharest becomes "Tehran" in every database, every VPN app, every compliance system, and every sanctions screening tool on the planet. This dossier examines who benefits, who is deceived, and what laws may be broken when a company manufactures countries that don't physically exist on its network.
Chapter 1: What Is a Geofeed and Why Should You Care
In 2020, the Internet Engineering Task Force published RFC 8805 โ "A Format for Self-Published IP Geolocation Feeds." The standard was designed to solve a legitimate problem: GeoIP databases often mislocate IP addresses, causing users to see wrong-language content, incorrect pricing, or unavailable services. RFC 8805 lets network operators publish a CSV file saying "these IPs are in this location" โ and GeoIP databases like MaxMind, IPinfo, IP2Location, and DB-IP consume these feeds to correct their records.
The format is simple:
Here's the critical design flaw: RFC 8805 has no verification mechanism. There is no validation that the IP actually routes to that country. There is no physical presence requirement. There is no audit. The network operator simply declares a location, and the world's geolocation databases update accordingly. It is a system built entirely on trust โ trust that is trivially exploited.
Finding: Unverified Geographic Claims
M247 Europe SRL publishes geoip.m247.ro/geofeeds.csv containing 2,191 entries mapping IP addresses to 116 countries. M247 operates physical infrastructure in approximately 30 data center locations across Europe, North America, and select Asian cities. The remaining 86+ countries in their geofeed have no corresponding physical infrastructure โ these are virtual locations where servers in Bucharest or Frankfurt are relabeled as endpoints in Tehran, Havana, Ashgabat, or Kinshasa.
Confidence: HIGH โ based on comparison of M247's published data center locations with their geofeed entries, corroborated by BGP routing data showing all traffic routes through Romanian, German, and US transit points.
The Trust Chain
When M247 publishes a geofeed entry saying 62.133.46.0/24 is in Tehran, Iran, the following cascade occurs:
- MaxMind GeoLite2 and GeoIP2 databases update to show these IPs as Iranian
- IP2Location ingests the feed and marks the block as Tehran
- IPinfo reflects the geofeed location in its API responses
- VPN applications using these databases display "Iran" or "Tehran" as the server location
- Streaming services geo-restrict content based on the GeoIP result
- Sanctions compliance tools may flag or permit traffic based on the reported country
- Law enforcement investigating traffic may attribute it to Iran when it's actually Romania
One CSV line in a file hosted on a Romanian server rewrites the geographic identity of 256 IP addresses across every geolocation system on the internet.
๐ Read Between the Lines #1: Who Asked for Iran?
Geofeed entries don't create themselves. Someone at M247 โ or a customer of M247 โ requested that 62.133.46.0/24 be labeled as Tehran, Iran. The RIPE database object for this block is named "M247-Iran" with the registrant entity "M247 Ltd Iran." This is not a typo. This is not an accident. This is a deliberate corporate structure: M247 created a named entity โ "M247 Ltd Iran" โ for the sole purpose of registering IP space as Iranian. The question isn't whether this is intentional. The question is: who is buying "Iranian" IP addresses from a Romanian company, and why?
Chapter 2: The Sanctioned Countries File
We downloaded M247's complete geofeed on June 19, 2025. Among 2,191 entries spanning 116 countries, we found active entries for the following sanctioned or heavily restricted nations:
๐จ OFAC Comprehensively Sanctioned Countries in M247 Geofeed
62.133.46.0/24
256 IPs โ "Tehran"
89.238.155.0/25
128 IPs โ "Havana"
91.238.70.0/24
256 IPs โ "Minsk"
10 entries
~1,280 IPs โ "Moscow"
The Full Sanctioned/Sensitive Inventory
| Country | CIDR Blocks | City | Sanctions Regime | RDAP Name |
|---|---|---|---|---|
| ๐ฎ๐ท Iran | 62.133.46.0/24 | Tehran | OFAC comprehensive | M247-Iran / "M247 Ltd Iran" |
| ๐จ๐บ Cuba | 89.238.155.0/25 | Havana | OFAC comprehensive | M247-Ltd-Cuba |
| ๐ง๐พ Belarus | 91.238.70.0/24 | Minsk | EU/UK sanctions, US sectoral | Belarus-1 / "us-fxcapital-1-mnt" |
| ๐ท๐บ Russia | 37.120.203.224/27, 185.247.69.0/24, 146.70.52.0/24, 5.180.138.0/24, 146.70.231.0/24, 135.136.44.0/24 + IPv6 | Moscow | US/EU sectoral sanctions | Various M247 entities |
| ๐น๐ฒ Turkmenistan | 217.138.10.0/25 + IPv6 | Aลgabat | US targeted sanctions | โ |
| ๐ฟ๐ผ Zimbabwe | 135.136.25.0/25 + IPv6 | Harare | US/EU targeted sanctions | โ |
| ๐จ๐ฉ Congo DRC | 135.136.24.128/25 + IPv6 | Kinshasa | US targeted sanctions | โ |
| ๐ป๐ช Venezuela | 3 entries | โ | OFAC sectoral sanctions | RDAP country: VE |
| ๐ฌ๐ณ Guinea | 135.136.25.128/25 + IPv6 | Conakry | โ | โ |
| ๐ญ๐น Haiti | 66.234.154.128/25 | Haiti | โ | โ |
| ๐ฑ๐ง Lebanon | 66.234.156.128/25 | Lebanon | Hezbollah-specific sanctions | โ |
| ๐บ๐ฟ Uzbekistan | 217.138.10.128/25 + IPv6 | Tashkent | โ | โ |
| ๐น๐ฏ Tajikistan | 217.138.89.128/25 + IPv6 | Dushanbe | โ | โ |
| ๐ฐ๐ฟ Kazakhstan | 7 entries | โ | โ | โ |
| ๐ต๐ฐ Pakistan | 4 entries | โ | โ | โ |
| ๐ฐ๐ญ Cambodia | 7 entries | โ | โ | โ |
The pattern is unmistakable. M247 has systematically created virtual endpoints in countries where it has no physical infrastructure, including four nations under comprehensive US sanctions. These are not errors โ they are named RIPE objects with dedicated entities.
๐ฌ Evidence: The RDAP Registrations
RIPE RDAP queries reveal the corporate structure behind these virtual countries:
- 62.133.46.0/24 (Iran): RIPE object name
M247-Iran, registrant entity"M247 Ltd Iran", technical contact"M247 Europe", maintainerGLOBALAXS-MNT - 89.238.155.0/25 (Cuba): RIPE object name
M247-Ltd-Cuba, registrant entity"M247 Europe SRL", maintainerM247-EU-MNT - 91.238.70.0/24 (Belarus): RIPE object name
Belarus-1, registrant entity"us-fxcapital-1-mnt"โ a different entity entirely, suggesting the Belarus block may be leased to or managed by a third party
The creation of named RIPE objects โ "M247-Iran" and "M247-Ltd-Cuba" โ demonstrates premeditated intentionality. These are not inherited legacy allocations. They are purpose-built registrations for virtual presence in sanctioned countries.
Chapter 3: The Sanctions Framework
The US Treasury's Office of Foreign Assets Control (OFAC) administers comprehensive sanctions programs against Iran, Cuba, North Korea, Syria, and โ since 2022 โ broad sectoral sanctions against Russia and Belarus. These sanctions are not suggestions. They carry criminal penalties of up to $1 million and 20 years imprisonment per violation (International Emergency Economic Powers Act, 50 U.S.C. ยง 1705).
What OFAC Prohibits
Under the Iranian Transactions and Sanctions Regulations (31 CFR Part 560) and the Cuban Assets Control Regulations (31 CFR Part 515), the following are prohibited for US persons:
- Exportation of services to Iran or Cuba, including telecommunications services (ยง 560.204)
- Facilitation by a US person of transactions by non-US persons that the US person could not directly undertake (ยง 560.208)
- Evasion or avoidance of any prohibition, including through the use of intermediaries (ยง 560.203)
- Dealing in property in which Iran or Cuba has an interest (ยง 560.211)
Where M247 Intersects
M247 Europe SRL is a Romanian company โ not directly a US person. But since January 2023, M247 has been wholly owned by Macquarie Group, one of Australia's largest investment banks with $945 billion AUD in assets under management (as of March 2025). Macquarie operates extensively in the United States through:
- Macquarie Capital (USA) Inc. โ registered SEC broker-dealer
- Macquarie Investment Management โ SEC-registered investment adviser
- Delaware Investments โ US mutual fund complex (acquired 2009)
- Waddell & Reed โ US wealth management (acquired 2021)
- Macquarie Infrastructure Corp (NYSE: MIC) โ US-listed infrastructure fund
- Green Investment Group โ US renewable energy investments
As a company with substantial US operations, US employees, US-registered entities, and US-dollar transactions passing through the US financial system, Macquarie falls under OFAC jurisdiction. Its subsidiary โ M247 โ operates IP blocks explicitly labeled as "Iran" and "Cuba."
Finding: Potential Sanctions Exposure
Macquarie Group, through its wholly-owned subsidiary M247 Europe SRL, maintains dedicated IP address blocks registered as "M247-Iran" (entity: "M247 Ltd Iran") and "M247-Ltd-Cuba" in RIPE's public database. These blocks are published via RFC 8805 geofeed as Tehran and Havana endpoints. Macquarie's extensive US operations, including SEC-registered entities and NYSE-listed funds, create OFAC jurisdictional nexus. Whether these virtual locations constitute "exportation of services" to sanctioned countries under 31 CFR Part 560 is a question that has never been tested โ but the exposure exists.
Confidence: HIGH for the factual infrastructure arrangement. MEDIUM for sanctions violation โ no OFAC enforcement precedent exists for virtual VPN locations specifically.
๐ Read Between the Lines #2: The $945 Billion Question
Macquarie Group manages $945 billion AUD in assets (approximately $620 billion USD). Its infrastructure investment division has acquired toll roads, airports, data centers, and telecommunications companies across five continents. M247 was acquired in January 2023 as part of Macquarie's digital infrastructure strategy.
A bank of this size does not acquire a company without compliance due diligence. Macquarie's legal team would have reviewed M247's customer base, its network topology, and its RIPE registrations. They would have seen "M247-Iran" and "M247-Ltd-Cuba" in the registry. The question is not whether they knew โ the question is why they proceeded anyway.
One possibility: the revenue from virtual locations is negligible compared to the VPN transit business, and the compliance risk was assessed as low because no enforcement precedent exists. Another possibility: the virtual locations serve a customer who brings enough revenue to justify the risk. A third possibility: nobody at Macquarie's compliance department knows what a geofeed is, because the intersection of network engineering and sanctions law is a gap that almost nobody in the financial industry understands.
Chapter 4: The 116-Country Illusion
M247 claims presence in 116 countries. No company on earth operates physical data centers in 116 countries. For context:
- Amazon Web Services: 33 regions, ~100 availability zones
- Microsoft Azure: 60+ regions
- Google Cloud: 39 regions
- Equinix (world's largest data center company): 70+ metros in 32 countries
- M247 (a Romanian ISP with ~90 employees): 116 countries
The gap between M247's physical footprint and its geofeed claims is not a rounding error โ it is the entire business model. Here is the distribution of M247's geofeed entries by category:
| Category | Countries | Entries | Physical Infrastructure |
|---|---|---|---|
| Core Markets (US, UK, DE, FR, NL, RO) | 6 | ~1,012 | Yes โ owned/leased data centers |
| Secondary Europe (ES, IT, PL, CH, etc.) | ~18 | ~440 | Partial โ colocation in some |
| Asia-Pacific (JP, SG, HK, AU) | ~8 | ~180 | Partial โ likely colocation |
| Virtual Locations (exotic, sanctioned) | ~84 | ~219 | None |
Approximately 72% of the countries in M247's geofeed are virtual โ servers physically located in Romania or Germany, relabeled as endpoints in Mongolia, Brunei, Papua New Guinea, or Haiti.
Finding: Systematic Geography Fabrication
M247's geofeed contains entries for 116 countries while operating physical infrastructure in approximately 30. The remaining 86 countries are fabricated geolocation claims โ servers in European data centers relabeled as endpoints in countries where M247 has no presence. This isn't virtual location as the VPN industry defines it; it is industrialized geography fraud at internet infrastructure level.
The Exotic Locations Map
Countries in M247's geofeed where no reasonable person could believe they operate physical infrastructure:
Ulaanbaatar
Bandar Seri Begawan
"Papua New Guinea"
"Haiti"
Vientiane
โ
Victoria
โ
โ
โ
โ
โ
Note the geofeed quality itself โ Haiti's "city" is listed as "Haiti" and Papua New Guinea's postal code is "123-151." These entries were created to fill a dropdown menu in a VPN app, not to describe physical infrastructure.
๐ฎ Conspirative Question #1: What If the Virtual Countries Aren't Just for VPN Users?
The conventional explanation is straightforward: VPN providers want to offer exotic locations to attract subscribers. "Connect to Brunei!" sells better than "Connect to another Bucharest server." But this explanation has a problem.
Consider: who wants to appear to be in Mongolia? Who benefits from traffic that looks like it originates from Papua New Guinea? These aren't just consumer features โ they are attribution laundering tools. A state actor conducting cyber operations who routes through a "Mongolian" VPN endpoint creates a false trail pointing to Ulaanbaatar instead of [actual country]. A sanctioned entity whose traffic appears to come from Brunei instead of Iran can potentially bypass automated screening.
The virtual country isn't just a product feature. It is a counterfeit passport for internet traffic.
Chapter 5: The Iran Block โ Anatomy of "M247-Iran"
Of all the virtual countries in M247's geofeed, Iran requires the deepest examination. The RIPE registration tells a story:
๐ฌ Evidence: RIPE RDAP Record for 62.133.46.0/24
- Network name: M247-Iran
- IP range: 62.133.46.0 โ 62.133.46.255 (256 addresses)
- Registrant: "M247 Ltd Iran" (entity handle via GLOBALAXS-MNT)
- Technical contact: "M247 Europe" (Bucharest, Romania)
- Abuse contact: "M247 Europe" โ abuse@m247.com
- Maintainer: GLOBALAXS-MNT
- Geofeed entry:
62.133.46.0/24,IR,,Tehran,1981227283
Note the maintainer: GLOBALAXS-MNT โ not M247's standard maintainer (M247-EU-MNT). GLOBALAXS was a legacy UK-registered ISP. Its use here suggests this IP block predates M247's current corporate structure and may have been inherited through acquisition. But the geofeed entry is actively maintained โ it appears in the current (2025) CSV file, meaning someone is actively choosing to keep "Iran" in the geolocation database.
What Happens When Traffic Is "From Iran"
When a VPN user connects to 62.133.46.0/24, the following occurs:
- Their traffic exits from a server in Romania (where the actual hardware sits)
- Every website they visit sees an IP that every GeoIP database on earth identifies as "Tehran, Iran"
- Content geo-restricted to Iran becomes accessible (Iranian streaming services, government portals, bank websites)
- Content geo-blocked from Iran becomes inaccessible โ unless the destination doesn't geo-filter
- Any monitoring system logging the traffic records it as Iranian-origin
- Any sanctions compliance system screening for Iranian IP addresses will flag this traffic
The GLOBALAXS Connection
The GLOBALAXS-MNT maintainer appears in multiple M247-related IP registrations. Global AXS Ltd was a UK-registered ISP (company number 06475375) that was part of M247's acquisition trail. The use of this legacy maintainer for the Iran block suggests one of two things:
- Option A: The Iran registration was created under Global AXS and inherited by M247. M247 has chosen to maintain it rather than decommission it.
- Option B: The GLOBALAXS-MNT maintainer is used for sensitive registrations that M247 prefers to distance from its primary brand, providing an additional layer of corporate separation.
๐ Read Between the Lines #3: "M247 Ltd Iran" โ A Company That Shouldn't Exist
The RDAP record lists the registrant entity as "M247 Ltd Iran." This name implies a legal entity โ a subsidiary or branch called "M247 Ltd" registered in or for Iran. But M247 doesn't appear in any Iranian corporate registry. There is no "M247 Ltd Iran" registered with Iran's Corporate Registration Office. This is a RIPE database label, not a legal entity โ but it is designed to look like one. It provides the illusion of legitimate corporate presence in a country where M247 has no presence whatsoever.
Why would M247 create a fictitious entity name for a RIPE registration? Because RIPE's registration framework expects a named entity for each IP allocation. By creating "M247 Ltd Iran," they satisfy the bureaucratic requirement while manufacturing the appearance of legitimate Iranian operations. It is a Potemkin company โ a facade that exists only in a database.
๐ฎ Conspirative Question #2: Who Pays for Iranian IP Addresses?
IP address blocks cost money to maintain. RIPE charges annual membership fees, and each IP allocation has associated costs. Someone is paying to keep 256 Iranian IP addresses alive on M247's network. The VPN industry answer is that NordVPN or Mullvad wants an "Iran" option in their location list. But consider the alternative.
The Iranian government operates one of the world's most sophisticated internet censorship systems โ the National Information Network (SHOMA). Iran's internet is heavily filtered, with all international traffic passing through government-controlled gateways. For Iranian citizens, a VPN that appears to originate from inside Iran but actually exits in Romania offers a way to bypass internal censorship while maintaining an Iranian IP address.
But there's a darker possibility: Iranian intelligence services (MOIS, IRGC-affiliated entities) could use Romanian-hosted "Iranian" endpoints to conduct operations that appear to originate from Iran โ creating a false flag that points at themselves. Why? Because operations conducted from "Iran" trigger different analytical pathways than operations from Romania. An analyst seeing Iranian IPs assumes a different threat model than one seeing Romanian IPs. The virtual location doesn't just deceive GeoIP databases โ it deceives the analytical frameworks that interpret network intelligence.
Chapter 6: The Cuba Block โ "M247-Ltd-Cuba"
Cuba's internet infrastructure is controlled by ETECSA (Empresa de Telecomunicaciones de Cuba S.A.) โ the state telecommunications monopoly. Cuba has approximately 7.6 million internet users (2023 estimate), with connectivity primarily through mobile data and wifi hotspots. International bandwidth is limited and expensive.
Against this backdrop, M247 โ a Romanian company โ maintains a block of 128 IP addresses (89.238.155.0/25) labeled as "Havana, Cuba" in its geofeed. The RIPE registration is explicit: object name "M247-Ltd-Cuba", maintainer M247-EU-MNT.
Cuba's Sanctions Profile
Cuba has been under US sanctions since 1962 โ the longest-running embargo in modern history. The Cuban Assets Control Regulations (31 CFR Part 515) prohibit:
- Any financial transaction with Cuban persons or entities
- Export of goods, services, or technology to Cuba (with limited exceptions for telecommunications since 2015)
- Travel-related transactions (with specific license categories)
The Obama administration's 2015 relaxation included a general license for telecommunications services to Cuba (ยง 515.578). However, this license specifically authorizes activities that improve Cuban people's access to communications โ it was designed for companies physically installing infrastructure in Cuba, not for companies relabeling European servers as Cuban endpoints.
Finding: Questionable Application of Telecommunications License
M247's "Cuba" block doesn't connect Cuban citizens to the internet. It creates virtual endpoints that make non-Cuban traffic appear to originate from Cuba. This is the inverse of what the OFAC general license for telecommunications services was designed to authorize. Instead of bringing connectivity to Cuba, it brings Cuba's geographic identity to servers in Romania.
Chapter 7: The Belarus Anomaly
The Belarus block (91.238.70.0/24, 256 IPs) presents a different pattern. While Iran and Cuba are maintained under M247's own entities, Belarus is registered to "us-fxcapital-1-mnt" โ a completely different RIPE maintainer.
๐ฌ Evidence: Belarus Registration Discrepancy
- Object name: Belarus-1
- Registrant maintainer: us-fxcapital-1-mnt (NOT M247's maintainer)
- Administrative/Technical contact: "Support Team" (generic)
- Abuse contact: "Abuse-C Role" (generic)
This block appears to be leased or delegated from M247's address space to a third party operating under "us-fxcapital-1-mnt." The "us-" prefix in the maintainer name suggests a US-based entity. If a US entity is operating IP address space labeled as Belarusian, the sanctions exposure becomes significantly more direct โ US persons are prohibited from most transactions with Belarus under Executive Order 14038 (August 2021) and the Belarus sanctions regulations.
Belarus Sanctions Context
Belarus sanctions intensified after the disputed 2020 election and Belarus's role in facilitating Russia's 2022 invasion of Ukraine:
- EO 14038 (August 2021): Broad sanctions targeting Belarusian government and economy
- EU sanctions: Comprehensive economic restrictions since 2021
- UK sanctions: Aligned with EU measures
- Sectoral sanctions: Targeting potash, petroleum, financial, and technology sectors
A US-based entity (indicated by "us-fxcapital-1-mnt") operating IP addresses geolocated to Belarus raises direct sanctions questions that do not require the Macquarie jurisdictional analysis โ this is potentially a US person providing services to/appearing as a Belarusian entity.
๐ฎ Conspirative Question #3: What Is "FX Capital" Doing in Belarus?
The maintainer name "us-fxcapital-1-mnt" suggests an entity related to foreign exchange (FX) capital โ a financial services firm. Financial services to Belarus are explicitly sanctioned under multiple US executive orders. If "FX Capital" is indeed a financial services entity, its operation of a Belarusian-labeled IP block on M247's network creates a remarkably direct sanctions exposure.
Consider the use case: a "Belarusian" VPN endpoint could allow a user to access Belarusian banking systems, government portals, or state media from anywhere in the world while appearing to be in Minsk. For a sanctioned Belarusian entity trying to conduct financial transactions, this is a compliance-evasion tool. For a Western intelligence agency monitoring Belarusian targets, it is a surveillance vector. For "FX Capital" โ whatever that entity actually is โ it is a sanctions liability hiding in plain sight in RIPE's database.
Chapter 8: The Russia Portfolio
Russia presents the largest virtual-location portfolio in M247's sanctioned-country inventory: 10 geofeed entries comprising approximately 1,280 IPv4 addresses plus IPv6 allocations, all mapped to "Moscow."
| CIDR Block | Type | City | Postal Code | Size (IPs) |
|---|---|---|---|---|
37.120.203.224/27 | IPv4 | Moscow | 111020 | 32 |
185.247.69.0/24 | IPv4 | Moscow | 123060 | 256 |
146.70.52.0/24 | IPv4 | Moscow | 123060 | 256 |
5.180.138.0/24 | IPv4 | Moscow | โ | 256 |
146.70.231.0/24 | IPv4 | Moscow | 123060 | 256 |
135.136.44.0/24 | IPv4 | Moscow | 123060 | 256 |
| Plus 4 IPv6 /48 blocks | ~281 trillion | |||
Since February 2022, Russia has been subject to the most extensive sanctions program since the Cold War. The EU, US, UK, Australia, Japan, and Canada have imposed coordinated sanctions targeting Russia's financial sector, energy exports, technology access, and trade. Providing IT infrastructure services to Russia is restricted under multiple legal frameworks.
M247's 1,280 Russian virtual IPs exist in a legal gray zone: the servers are physically in the EU, the traffic exits from Romania or Germany, but every database on earth says these IPs are in Moscow. For sanctions compliance purposes, is a "Russian" VPN endpoint a service to Russia? For law enforcement purposes, is traffic from these IPs "Russian" โ and should it be treated as such in investigations?
๐ Read Between the Lines #4: Moscow Postal Code 123060
Five of the six Russian entries share postal code 123060. This is the postal code for the Khoroshyovsky District in northwest Moscow โ home to the Moscow International Business Center (Moscow City), Russia's financial district. The one outlier uses postal code 111020, which corresponds to the Lefortovo District โ historically associated with the FSB's Lefortovo prison and the Russian defense industry cluster.
These aren't random postal codes. Someone chose the Moscow financial district and a security-service-adjacent district as the stated locations for virtual servers that physically sit in Romania. The postal code selection suggests knowledge of Moscow's geography โ and potentially a signal about intended use.
Chapter 9: The Discrepancy Matrix โ Where Sources Disagree
Our threat intelligence database reveals a systematic pattern: M247 IPs where the BGP-derived country (where the traffic actually routes) differs from the RDAP-registered country (where the IP is supposed to be). This is the discrepancy that started this investigation.
| IP | BGP Route | RDAP Country | Geofeed | Threat Score | Ports |
|---|---|---|---|---|---|
95.181.237.131 | ๐ท๐ด Romania | ๐ป๐ช Venezuela | VE | 14.4 | 443, 1337, 6443, 8080, 8443 |
95.181.237.142 | ๐ท๐ด Romania | ๐ป๐ช Venezuela | VE | 12.8 | 1337, 6443, 8080, 8443 |
95.181.234.133 | ๐ท๐ด Romania | ๐ถ๐ฆ Qatar | QA | 11.2 | 443, 1337, 8080, 8443 |
95.181.238.191 | ๐ท๐ด Romania | ๐ง๐ธ Bahamas | BS | 7.6 | 443, 1337, 6443, 8443 |
95.181.239.137 | ๐ท๐ด Romania | ๐ฑ๐ฐ Sri Lanka | LK | 7.2 | 443, 1337, 6443, 8443 |
91.90.126.156 | ๐ท๐ด Romania | ๐ต๐ฆ Panama | PA | 6.8 | 443, 6443, 8080, 8443 |
146.70.65.18 | ๐ท๐ด Romania | ๐ณ๐ฌ Nigeria | NG | 5.6 | 443, 6443, 8080, 8443 |
91.90.124.159 | ๐ท๐ด Romania | ๐ฎ๐ช Ireland | IE | 3.6 | 1337, 6443, 8080, 8443 |
188.241.80.136 | ๐ท๐ด Romania | ๐จ๐ญ Switzerland | CH | 14.0 | 1337, 8080, 8443 |
Every single one of these IPs is physically in Romania (BGP routing through Romanian networks) but administratively claimed as Venezuela, Qatar, Bahamas, Sri Lanka, Panama, Nigeria, Ireland, or Switzerland. Note the common port pattern: 443, 1337, 6443, 8080, 8081, 8443. Port 1337 is a common VPN/proxy service port. Port 6443 is the Kubernetes API server port. Ports 8080/8443 are alternative HTTP/HTTPS ports.
These are VPN endpoints running on Kubernetes infrastructure. The entire virtual country system is orchestrated through containerized deployments โ spin up a pod, assign it an IP from the "Venezuela" pool, publish it in the geofeed, and a server in Bucharest becomes Caracas.
Finding: Containerized Country Manufacturing
The common port signature (6443 โ Kubernetes API) across all discrepant M247 IPs indicates these virtual locations run as Kubernetes pods. The infrastructure is designed for rapid deployment and scaling: need another "Qatar" endpoint? Deploy a pod, assign the IP, update the geofeed CSV. The country isn't a physical location โ it's a configuration parameter in a deployment manifest.
Chapter 10: The Consumer Deception
When a VPN user selects "Iran" or "Bahamas" or "Mongolia" in their app, they believe they are connecting to a server in that country. The VPN industry has introduced the concept of "virtual locations" to partially address this โ NordVPN, for example, uses a small globe icon to indicate servers that aren't physically where they claim to be.
But the disclosure is inadequate. Consider what the user actually gets:
| What User Expects | What User Gets |
|---|---|
| Server physically in Iran | Server in Romania, geofeed says Iran |
| Routing through Iranian infrastructure | Routing through Romanian/German infrastructure |
| Speed benefits of local connectivity | No speed benefit โ server is 5,000 km away |
| Access to Iranian content/services | May work if the service checks GeoIP only |
| Iranian IP for research/journalism | IP flagged as Iranian โ may trigger scrutiny |
| Privacy from their own ISP | This part actually works (the tunnel is real) |
The VPN tunnel is real. The encryption is real. The country is not.
๐ฎ Conspirative Question #4: What If Virtual Locations Are a Feature for Compliance Arbitrage?
Consider a business scenario: a company needs to test whether its services are accessible from sanctioned countries (compliance testing). Instead of hiring a consultant in Tehran, they connect to "Iran" through their VPN. Their compliance report says "tested from Iranian IP addresses" โ but the traffic never left the EU.
This creates a compliance theater โ the appearance of testing without the reality. If a company reports to regulators that their geo-restrictions work "as tested from Iran," but the testing was conducted from a Romanian server with an Iranian IP label, the entire compliance framework is built on a manufactured geography.
Now scale this: how many compliance reports, how many sanctions screening tests, how many geo-restriction verifications are conducted through virtual VPN locations? The answer is unknowable, but the infrastructure for systematic compliance fraud exists and is commercially available for $3-12/month through any VPN subscription.
Chapter 11: The RFC 8805 Problem โ A Standard Without Verification
RFC 8805 was designed with good intentions. GeoIP databases are notoriously inaccurate โ a server in France might be identified as being in Belgium, causing the user to see Dutch-language content. Self-published geofeeds let operators correct these errors.
But the standard has a fundamental design flaw: it trusts the operator.
- No verification: The geofeed is a CSV file hosted by the operator. Nobody validates that the IP actually routes to the claimed location.
- No audit trail: Geofeed changes are not logged by consumers. A company can relabel IPs from "Romania" to "Iran" and back without any public record.
- No authorization check: The standard doesn't verify that the operator has legal authority to claim presence in the declared country.
- No sanctions screening: GeoIP database companies consume geofeeds without checking whether the claimed locations involve sanctioned jurisdictions.
- No physical verification: There is no requirement (or mechanism) to verify that any infrastructure actually exists in the claimed location.
RIPE NCC has added geofeed support to its database objects (inetnum and inet6num), allowing operators to reference their geofeed URLs directly in the registry. This gives the geofeed the imprimatur of a Regional Internet Registry โ but RIPE doesn't validate the content any more than the GeoIP databases do.
Finding: RFC 8805 Enables Sanctions-Regime Circumvention
The geofeed standard, as currently implemented, allows any network operator to claim any geographic location for any IP address with zero verification. This creates a mechanism by which:
- IP addresses can be labeled as originating from sanctioned countries, potentially triggering or evading sanctions screening
- Traffic attribution can be falsified at the GeoIP database level, affecting law enforcement investigations
- Compliance testing can be conducted on manufactured geography, producing unreliable results
- Virtual country labels can be changed at will, without audit trail, creating a moving target for enforcement
RFC 8805 is, in effect, a standardized mechanism for geographic fraud that has been adopted by every major GeoIP database provider.
๐ Read Between the Lines #5: Who Benefits from No Verification?
Standards don't write themselves. RFC 8805 was authored by network operators who had a specific problem (GeoIP inaccuracy) and a specific solution (self-correction). The absence of verification wasn't an oversight โ it was a design choice. Verification would require infrastructure (measurement probes, latency testing, BGP analysis) that would add cost and complexity.
But who benefits most from the absence of verification? The same operators who publish the feeds. M247 can claim 116 countries because nobody checks. And the GeoIP database companies have no incentive to check โ their business model is selling geolocation data, and more entries means more coverage means a better product to sell. MaxMind's value proposition improves when it can accurately (per the geofeed) locate IPs in Mongolia and Haiti, even if those locations are fabricated.
Everyone in the chain benefits from the fiction. The only losers are the users who believe the data, the regulators who rely on it, and the analysts who build threat models on it.
Chapter 12: The Macquarie Compliance Question
Macquarie Group acquired M247 in January 2023. As one of Australia's "Big Four" financial institutions (alongside ANZ, CommBank, NAB, and Westpac), Macquarie is subject to:
- Australian sanctions: Autonomous Sanctions Act 2011, UN sanctions via Charter of the United Nations Act 1945
- US sanctions: OFAC jurisdiction through US-registered subsidiaries and US-dollar transactions
- EU sanctions: Through European operations and EUR-denominated transactions
- UK sanctions: Through UK operations (M247's original headquarters was Manchester)
- APRA prudential standards: Australian Prudential Regulation Authority oversight
Australia's autonomous sanctions regime includes comprehensive sanctions against Iran (Autonomous Sanctions (Designated Persons and Entities and Declared Persons โ Iran) List 2012) and Russia/Belarus (expanded post-2022). Australia also maintains targeted sanctions against Zimbabwe and other countries present in M247's geofeed.
The Compliance Gap
Macquarie's 2024 Annual Report discusses ESG commitments, climate targets, and governance frameworks. It does not mention M247's geofeed, virtual locations, or the fact that a wholly-owned subsidiary maintains IP address blocks labeled "Iran" and "Cuba" in a public internet registry.
This omission creates several risk vectors:
- Regulatory risk: If OFAC, APRA, or EU sanctions authorities examine M247's RIPE registrations, the "M247 Ltd Iran" entity name alone could trigger an investigation
- Reputational risk: Public disclosure of Iran/Cuba/Belarus virtual locations could affect Macquarie's ESG ratings and institutional investor confidence
- Legal liability: If M247's virtual locations are used to facilitate sanctions evasion โ even unknowingly โ Macquarie as parent company faces potential secondary sanctions
- Insurance risk: Macquarie's D&O insurance may exclude sanctions-related liabilities, leaving directors personally exposed
๐ฎ Conspirative Question #5: Did Macquarie's Due Diligence Catch This?
When a $945 billion investment bank acquires a company, the due diligence process is exhaustive. Teams of lawyers, accountants, and consultants review every contract, every liability, every regulatory exposure. M247's RIPE registrations โ including "M247-Iran" โ are public records accessible to anyone with a web browser.
Three scenarios:
- Scenario A: Due diligence identified the Iran/Cuba registrations but assessed the risk as manageable โ perhaps because no enforcement precedent exists for virtual VPN locations. The registration was retained as a calculated risk.
- Scenario B: Due diligence did not examine RIPE registrations because the intersection of internet routing and sanctions law is a blind spot in traditional M&A due diligence. The lawyers checked contracts and financials; nobody checked the geofeed.
- Scenario C: Due diligence flagged it, but the decision was made at a level above compliance. The VPN transit business is too lucrative, and the Iran/Cuba blocks are too small to justify disrupting the acquisition. The risk was accepted, not assessed.
Whichever scenario is true, the result is the same: one of the world's largest investment banks owns a company that maintains IP address space explicitly labeled as "Iran" in a public registry, accessible to any sanctions regulator who knows where to look.
Chapter 13: The Broader Implications โ When Geography Is a Database Entry
This investigation began with a simple observation: M247 IPs in our honeypot showed different countries depending on which data source we consulted. BGP said Romania. RDAP said Venezuela. The geofeed said Qatar. This discrepancy led us to M247's geofeed file, which led us to Iran, Cuba, Belarus, and 113 other countries that exist only as lines in a CSV file.
The implications extend far beyond M247:
For Law Enforcement
Every investigation that uses GeoIP data to attribute network activity to a country is potentially contaminated by geofeed manipulation. An "Iranian" cyber attack may originate from Romania. A "Mongolian" phishing campaign may be a European operation. The investigative assumption โ that an IP's geographic location reflects something real about the attacker โ is fundamentally undermined by the virtual location industry.
For Sanctions Enforcement
Sanctions screening systems that rely on GeoIP databases are operating on potentially fabricated data. A transaction screening system that flags "Iranian" IP addresses will flag M247's virtual Iranian endpoints โ creating both false positives (legitimate VPN users incorrectly flagged) and, more dangerously, potential false negatives (actual Iranian traffic routed through non-Iranian virtual locations to avoid detection).
For Intelligence Analysis
Threat intelligence that attributes activity to countries based on GeoIP data is building analytical frameworks on manufactured geography. A threat report claiming "increased Iranian cyber activity" may actually reflect increased VPN usage through M247's Romanian servers. The entire discipline of geographically-attributed threat intelligence is only as reliable as the geolocation data it depends on.
For Internet Governance
RFC 8805 was designed to solve a legitimate problem. But its adoption without verification has created a larger problem: network operators can now claim any geography for any IP address, and the world's databases will reflect that claim. RIPE NCC, as the registry that hosts these geofeed-referenced objects, bears responsibility for providing a framework that enables geographic misrepresentation without safeguards.
Finding: Systemic Geographic Integrity Failure
The internet's geographic attribution system โ the chain from RIPE records through geofeeds to GeoIP databases to compliance tools โ contains no verification at any layer. Network operators can, and do, claim geographic locations that are entirely fabricated. This systemic failure affects sanctions enforcement, law enforcement investigations, threat intelligence analysis, and consumer protection. M247's 116-country geofeed is the most visible example, but every network operator publishing a geofeed has the same capability.
Chapter 14: The Scale of the Problem
M247 is not alone. To understand the scope, consider the VPN industry's virtual location practices:
| Provider | Total "Locations" | Physical Servers | Virtual % | Discloses? |
|---|---|---|---|---|
| NordVPN | 111 countries | ~65 countries | ~42% | Partial (globe icon) |
| Surfshark | 100 countries | ~50 countries | ~50% | Yes (labeled) |
| ExpressVPN | 105 countries | ~45 countries | ~57% | Yes (less than 3%) |
| CyberGhost | 100 countries | ~35 countries | ~65% | Partial |
| PureVPN | 78 countries | ~30 countries | ~62% | Minimal |
The industry standard is to offer more "countries" than you have servers. Virtual locations are the norm, not the exception. M247 is the infrastructure provider that makes this possible โ its geofeed is the factory where virtual countries are manufactured at wholesale scale.
๐ฎ Conspirative Question #6: Is the Virtual Location Industry a Feature or a Bug of the Sanctions System?
Sanctions work by restricting access to financial and commercial systems based on geographic and entity identification. Virtual locations fundamentally undermine geographic identification. If anyone with $12/month can become "Iranian" or "Cuban" in every database, the geographic pillar of sanctions enforcement is structurally compromised.
The optimistic reading: this is an unintended consequence of consumer VPN marketing, and regulators will eventually catch up.
The pessimistic reading: the virtual location industry exists because there is demand for geographic identity fraud, and that demand comes from entities โ state and private โ who benefit from the erosion of geographic sanctions enforcement. The VPN industry doesn't just profit from sanctions arbitrage. It enables it at infrastructure level, sold as consumer privacy, funded by subscription revenue.
Chapter 15: Methodology and Sources
๐ Data Sources and Methodology
- M247 Geofeed: Downloaded 2025-06-19 from
https://geoip.m247.ro/geofeeds.csvโ 2,191 entries, archived as artifact - RIPE RDAP: Queries for 62.133.46.0/24 (Iran), 89.238.155.0/25 (Cuba), 91.238.70.0/24 (Belarus) via rdap.db.ripe.net
- Honeypot Database: 47 M247-routed IPs (AS9009) in our threat_intel PostgreSQL database, with multi-source enrichment (AbuseIPDB, Shodan, GreyNoise, RDAP, Cymru)
- BGP Routing Data: Cymru BGP origin lookups confirming all virtual-location IPs route through Romanian/European transit
- RFC 8805: IETF standard specification at datatracker.ietf.org/doc/html/rfc8805
- OFAC Regulations: 31 CFR Parts 515 (Cuba), 560 (Iran), Executive Orders 13846, 14038 via treasury.gov/ofac
- Macquarie Group: 2024 Annual Report, SEC EDGAR filings, APRA regulatory disclosures
- Cross-references: TI-2026-023A (VPN Laundromat), 023B (The Backbone), 026F (The Sanctions Question)
Key Limitations
- We have not confirmed whether M247's Iran/Cuba blocks are actively in use by current VPN providers โ only that they exist in the geofeed and RIPE registry
- No OFAC enforcement precedent exists specifically for virtual VPN locations in sanctioned countries
- Macquarie's internal compliance assessment of M247's virtual locations is unknown
- We have not tracerouted live traffic through the Iran/Cuba blocks to confirm routing paths
- The "us-fxcapital-1-mnt" entity behind the Belarus block has not been independently verified
Chapter 16: Conclusions
M247 Europe SRL operates the internet's largest virtual country factory. Through a single CSV file โ a geofeed โ it instructs the world's geolocation databases to label Romanian and German servers as endpoints in 116 countries, including Iran, Cuba, Belarus, and Russia. The RIPE registry contains purpose-built entities โ "M247 Ltd Iran" and "M247-Ltd-Cuba" โ that exist solely to provide the appearance of legitimate operations in comprehensively sanctioned countries.
The geofeed mechanism (RFC 8805) that enables this contains no verification, no audit trail, and no sanctions screening. It is a system built entirely on trust, operating in an industry where trust is a commodity sold for $12/month.
Macquarie Group โ a $945 billion investment bank subject to sanctions regimes in Australia, the US, the EU, and the UK โ owns this infrastructure. Whether by design, by negligence, or by the structural gap between network engineering and compliance law, one of the world's most powerful financial institutions operates what may be the world's most accessible sanctions-circumvention infrastructure, published as a public CSV file hosted on a Romanian domain.
The virtual country is not a place. It is a database entry that tells every system on the internet โ every GeoIP lookup, every compliance check, every threat intelligence platform โ that a server in Bucharest is actually in Tehran. The server hasn't moved. The data has.
And in a world where geography is enforced by databases, changing the database is the same as changing the geography.