Singapore's Telecom Breach: What Telecom Operators in Southeast Asia Should Do Next

Summary

  • Singapore disclosed in February 2026 that the advanced persistent threat group UNC3886 used a zero-day exploit to get past a perimeter firewall and into its telecom networks. All four major operators were targeted, and the response ran for more than 11 months.
  • For operators across the region, the lesson is about exposure. The way in was a device facing the internet, and this group has hidden behind relay networks whose addresses can change within a month.

Key Facts

Attacker
UNC3886, which researchers including Mandiant link to China. Singapore did not name a country.
Targets
M1, SIMBA Telecom, Singtel and StarHub
Way in
A zero-day exploit used to bypass a perimeter firewall
Taken
A small amount of technical data, believed to be mainly network-related
Not affected
No evidence that customer records were accessed or services disrupted
Response
Operation Cyber Guardian: more than 100 defenders from agencies including CSA and IMDA, for more than 11 months

Singapore first disclosed in July 2025 that UNC3886 was attacking its critical infrastructure. According to its Cyber Security Agency (CSA), the attackers gained limited access to critical systems but “did not get far enough to have been able to disrupt services.”

Why It Matters

The firewall was the way in

Perimeter firewalls face the internet by design, so anyone scanning for them can find them. Mandiant describes UNC3886 as a group that "has historically targeted network devices and virtualization technologies with zero-day exploits," with interests focused on defense, technology and telecom organizations in the US and Asia.


Patching cannot close a flaw nobody knows about yet. What an operator can control is how much of its network an outsider can see and reach.

Why blocking by address falls behind

China-nexus groups increasingly route attacks through operational relay box (ORB) networks: These are compromised routers, IoT devices, and leased servers, often end of life, that make attack traffic harder to trace back to the attacker.


UNC3886 has used this cover before. In a March 2025 report, Mandiant described backdoors on end-of-life Juniper routers, with one set of command servers believed to be staging nodes of an ORB network. Team Cymru notes those indicators were located in Singapore. Team Cymru also counted up to 42 ORB addresses communicating with the four operators' networks in a 30-day window.


These addresses do not last. Mandiant found an address can stay in an ORB network for as few as 31 days and warns that "IOC extinction is accelerating." Blocklists still have a place against known infrastructure. Against infrastructure that changes monthly, they fall behind.


What changes with Entropya​

Singapore's case started with a device the internet could see. Entropya's HIDE. HARDEN. VERIFY approach starts in the same place, by reducing what an outsider can find before protecting and verifying everything that remains. HIDE uses Digital Camouflage to keep infrastructure out of public view, HARDEN applies post-quantum cryptography (PQC) to protect traffic, and VERIFY authenticates every session.


Exposed perimeter
Scanner on the internet
Firewall or VPN gateway
Public IP Open ports DNS records
Core network

Visible devices can be found, probed and targeted.

With Digital Camouflage, powered by EEN
Scanner on the internet
Nothing to probe
No exposed IPs, ports or DNS records to find
Authorized userConnected through EEN
Randomized, one-way tunnels
IEGIron Edge Gateway
Authenticated session
Firewall or VPN gatewayOptional
Core network

Only authenticated sessions connect.

Figure 1. What an outsider can see: an exposed perimeter compared with Digital Camouflage


Entropya Encrypted Network (EEN) is infrastructure agnostic. It deploys on premises or in the cloud and runs over any internet connection. An Iron Edge Gateway (IEG) at the internet-facing edge authenticates systems into the EEN. If a firewall is retained in the architecture, the IEG complements it by making sure only authenticated sessions reach it. Because EEN operates at Layers 2 and 3 of the Open Systems Interconnection (OSI) model, everything above them works as before, now protected by Entropya.


Table 1. Exposures in the Singapore attack and how Entropya addresses them

The exposure With Entropya What it means for operators
A perimeter firewall faced the internet and was the way in Digital Camouflage, delivered by EEN and the IEG, keeps IP addresses, open ports and DNS records out of public view Fewer devices to find and probe, and less exposure to zero-day flaws
Network-related data was taken EEN separates source and destination over randomized, one-way, short-lived PQC-protected tunnels Much harder to learn how the network is built and communicates
Attack traffic hides behind relay addresses that change within a month Every session is dynamically authenticated before it connects, with no open ports to reach Protection that does not depend on blocklists keeping up
Traffic recorded today could be decrypted later EEN establishes a new key for every session using ML-KEM 1024 key encapsulation and renews it every two minutes by default Data in transit protected against harvest now, decrypt later


“The client's systems continue to operate normally, but it becomes much more difficult to use open-source intelligence, network analytics, or pattern-of-life analysis against their infrastructure.”

​Mr. Purta, Co-Founder and CEO, Entropya

​

Questions to ask your team

  • Which of our firewalls, VPN gateways and routers can be reached from the internet, and which run end-of-life software?
  • If one of them had an unknown flaw today, what could an attacker reach behind it?
  • Do we analyze flow data for traffic from residential and small-office relay addresses?
  • How much of our blocking relies on IP reputation, and how current is it?



Review your exposure

See what your network shows to outsiders

Find out which of your gateways, management paths and services are visible from the internet.

Talk to a Security Architect

Frequently Asked Questions