[DEEP RESEARCH] The Trusted Carrier Was Also the Attack Source
SilentAir turned carrier trust into an interception path. Test who can prove where the malicious signalling began.
A legitimate mobile operator can carry an attack—and, Enea reports, contain the node launching it. Its November 11 disclosure reconstructs SilentAir, a targeted interception operation active since before 2025. Malicious signalling changed subscriber routing so later calls and text messages could reach attacker-controlled destinations. For some targets, Enea observed two-factor authentication codes arriving immediately after interception began. That suggests attempted access to other accounts, not demonstrated account takeover. [1]
The new development is the reconstruction, not the first interception. For carrier responders and customers buying managed-core services, it raises a harder question than which address to block: who can establish what was running behind that address?
Our judgment: Containing malicious signalling and proving control of the originating node are separate jobs; an assurance review should demand evidence for the job it claims to complete.
We have moderate confidence in the case-specific internal-compromise conclusion. Enea says it observed network elements inside an operator both initiate and receive the attack commands, confirming compromise rather than external spoofing with copied replies. The public account does not expose those captures or identify the responsible executable. Enea recovered unauthorized-access artifacts but could not successfully analyze the hypothetical SilentAir binary. Its proposed LIMINAL PANDA connection remains unconfirmed; its China-nexus assessment is low-confidence. [1]
A valid address is not a clean process
Mobile operators exchange signalling to make roaming, calls and messaging work. SilentAir abused SS7 and Diameter, protocols used to exchange subscriber and routing information. A malicious location update could put an attacker-controlled destination in the path of subsequent communications. Here, “location” is a routing instruction—not, by itself, evidence of geographical tracking. [1]
A reply arriving at a legitimate operator does not prove the operator originated the request. External injection and copied or redirected responses are competing explanations. The useful step in Enea’s account is the paired observation of initiation and receipt inside the network. That strengthens the internal-source explanation; identifying the unauthorized process still requires another evidence layer.
For an analyst, the first useful request is therefore specific: take one suspicious transaction and ask where each observation was captured, in which direction, and how its identifiers and timing match. Then ask whether application, runtime or administrative records connect it to unauthorized execution. A source-address lookup cannot do that work.
A firewall can stop the conversation without settling who was speaking.
The continuation turns that distinction into an investigation and supplier-assurance test: what evidence separates the explanations, which owners must produce it, and what conclusion remains defensible when they cannot.
Follow one transaction across the custody boundary
Start with the suspicious transaction, not the vendor organization chart. Establish which records can explain its origin and return path, then identify who can preserve and examine them.