Fire Ant taught a Cisco IOS XR router to forward only log lines containing the word Health
Sygnia found the China-nexus group running packet captures, a tac_plus credential hook and two layers of log suppression on the gear that authenticates the rest of the estate, and it never established how the router was breached.
The Watch · Security desk
What happened
- Sygnia says the China-nexus actor it tracks as Fire Ant moved beyond VMware hypervisors into Cisco IOS XR routers, TACACS servers and Linux management hosts that route and authenticate high-value networks.
- On the TACACS server, an injector called acppid pushed a library into the live tac_plus process, hooked its connection-accept functions and handed session handles to a second process over a Unix socket.
- The activity follows Sygnia's July 2025 Fire Ant disclosure, which covered exploitation of VMware ESXi and vCenter before the group reached the network and management layers.
Why it matters
- Who's exposed exposure A hooked tac_plus process reads authentications for every device that trusts it, so credential rotation after this pattern has to cover the whole authenticated device population rather than the hosts with confirmed implants.
- What it limits constraint Telemetry generated and forwarded by the compromised device cannot serve as its own integrity check, which pushes router monitoring toward out-of-band collection and state-versus-config comparison.
- What's now possible capability Collection sits where endpoint agents do not run, giving the operator traffic-level visibility over trusted paths without touching a single monitored workstation or server.
- What it sets up precedent Sygnia describes the tac_plus injection as not previously public, which sets an expectation that library injection into live authentication daemons becomes a reusable pattern rather than one group's trick.
Next story · Security · 4h ago
Attackers pushed a backdoor through AOMEI Backupper's update servers in windows of 5 to 10 minutesConfirmed2 publishers
Sygnia found a component on the router that embedded a modified system library, checked each outgoing log message for the string Health, and forwarded it only when the string was present [5]. A collector watching that device does not fall silent. It keeps receiving healthy-looking messages from a live host while everything else is dropped at the source, which means the router's own syslog stream is worthless as evidence of the router's state.
The second layer targeted the operator rather than the collector. A separate component altered the command-execution path to append an `| exclude` filter to show commands, so an administrator inspecting the device saw a configuration with the attacker's tunnel edited out [6].
That matters for how the intrusion surfaced. The anomaly was a GRE tunnel interface operating with no running configuration and no commit history to explain its creation [4]. A change-control review reads commits. This tunnel had none, so nothing in the change record would have shown it; catching it required comparing observed interface state against configuration [19]. Sygnia did not identify how the actor first gained access to the router [17].
On the TACACS server, an injector named acppid loaded a malicious library into the running tac_plus process, hooked the functions that accept new connections, and passed live session handles to a second process over a local Unix socket [11]. Captured credentials went to `/var/log/.tacplus.acct`, obfuscated with a single-byte XOR key of 0xEF [12]. A single byte is 256 possible keys, so that file costs a responder nothing to decode once located; the obfuscation slows down a casual keyword search but not a real one [20]. Sygnia says this specific tac_plus library-injection technique has not been publicly described before [14], though Mandiant has documented UNC3886 deploying a TACACS+ sniffer called LOOKOVER and replacing the tac_plus daemon with a backdoored version [15].
Attribution is stated carefully in the report and should be repeated that way. Sygnia assesses strong overlap with public reporting on UNC3886 but does not make a conclusive attribution [3]. Mandiant, which first documented UNC3886, found no technical overlap with Salt Typhoon or Volt Typhoon [8]. The activity sits outside the Typhoon campaigns.
Egress is where the collection became traffic. Packet captures from multiple Cisco devices were uploaded to external FTP servers, one of which appeared to have been installed the same day the uploads took place [10]. Infrastructure with a one-day life is only caught by flow records that outlive it.
The concealment spanned five mechanisms: the syslog filter, the show-command exclusion, BridgeAgent posing as a Zabbix agent under a `zabbix_agent.service` systemd unit with its process disguised as `/usr/bin/gnome-shell` [16], the Medusa and REPTILE rootkits on the Linux management hosts [18], and the dotfile credential store. Four of those five sit below or beside the tooling most estates use to watch these hosts [21].
The reach claim stays bounded. Sygnia assessed the actor explored paths toward connected high-value environments including critical infrastructure, but activity there was limited to scanning and connection attempts, not confirmed compromise [2]. From the legacy Linux host reached through the tunnel, that probing hit SSH, HTTP, SMB and RDP on connected networks [13].
What to watch
- Whether Sygnia or Cisco publishes an initial access vector or CVE for the IOS XR foothold, which is still unexplained.
- Whether the tac_plus library-injection technique shows up in other clusters' tooling now that Sygnia has described it.
- Whether the scanning and connection attempts against connected critical infrastructure are later upgraded to confirmed compromise.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence68
- Adoption
- Not scored
- Hype gap+25
- Incentives55
- Confidence64
Perspective Coverage
6 publishers- Builder
- Builder 33%
- Operator
- Operator 53%
- Investor
- Investor 14%
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Fire Ant, a China-nexus cyber espionage actor, expanded a long-running campaign beyond VMware hypervisors to compromise Cisco IOS XR routers, TACACS servers, and Linux management hosts used to route, authenticate and manage high-value networks.
- [2]
Sygnia assessed the group used its foothold to explore paths to connected high-value environments including critical infrastructure, but activity against those networks was limited to scanning and connection attempts rather than confirmed compromise.
- [3]
Sygnia assessed the activity strongly overlaps with public reporting on UNC3886, a China-nexus espionage group known for targeting virtualization platforms and network edge devices, but said its report does not make a conclusive attribution.
- [4]
The investigation began with an anomaly on a Cisco IOS XR router, where a Generic Routing Encapsulation (GRE) tunnel interface was operating with no running configuration or commit history to explain how it had been created.
- [5]
The router malware was purpose-built for the IOS XR control plane rather than a generic Linux appliance; one component embedded a modified system library that checked each outgoing log message for the string Health and forwarded it only when the string was present.
- [6]
A separate component altered the router's command-execution path to append an | exclude filter to show commands, hiding the attacker's tunnel configuration from administrators inspecting the device.
- [7]
Sygnia, the incident response firm that investigated the intrusion, said the actor turned compromised routers into collection platforms, capturing network traffic, harvesting credentials and suppressing logging and telemetry defenders rely on to reconstruct an attack.
- [8]
Mandiant, which first documented UNC3886, has said it found no technical overlap between that group and the separate Chinese operations tracked as Salt Typhoon and Volt Typhoon.
- [9]
The 2026 activity follows Sygnia's July 2025 disclosure of Fire Ant, which detailed the group's exploitation of VMware ESXi and vCenter environments before it moved into the network and management layers.
- [10]
Fire Ant used the routers to capture PCAPs from multiple Cisco devices and uploaded them to external FTP servers, one of which appeared to have been installed the same day the uploads took place.
- [11]
On the TACACS server, Sygnia identified a credential-collection toolset it tracks as TacTap; an injector named acppid loaded a malicious library into the running tac_plus authentication process, hooked the functions that accept new connections, and passed live session handles to a second process over a local Unix socket.
- [12]
Captured credentials were written to /var/log/.tacplus.acct and lightly obfuscated with a single-byte XOR key of 0xEF.
- [13]
Tracing the tunnel led investigators to a legacy Linux system, from which Fire Ant ran repeated connection attempts and port probing against administrative and service ports on connected networks, including SSH, HTTP, SMB and RDP.
- [14]
Sygnia said that to its knowledge the specific tac_plus library-injection technique has not been publicly described before, making it a notable evolution of Fire Ant's TACACS-focused credential collection tradecraft.
- [15]
Mandiant has previously documented UNC3886 deploying a TACACS+ sniffer called LOOKOVER and replacing the tac_plus daemon with a backdoored version to log credentials.
- [16]
Sygnia recovered a second new tool, a Linux backdoor it called BridgeAgent, deployed on the tunnel-connected host and masquerading as a Zabbix monitoring agent; it persisted via a zabbix_agent.service systemd unit running as root, disguised its process as /usr/bin/gnome-shell, and polled attacker infrastructure over TLS on port 443 for commands and reverse-shell instructions.
- [17]
Sygnia did not identify how the actor first gained access to the router.
- [18]
Across the Linux management hosts, Fire Ant built a durable access layer using the open-source Medusa and REPTILE rootkits.
- [19]
Because the GRE tunnel interface was running with no configuration and no commit history, a review of the device's change record would not have contained it, so detection required comparing observed interface state against the stored configuration.
- [20]
A single-byte XOR key has 256 possible values, so the /var/log/.tacplus.acct credential file can be decoded by a responder at negligible cost once the file is found.
- [21]
The reporting documents five distinct concealment mechanisms across the router, TACACS and Linux tiers: the Health-string syslog filter, the show-command exclude filter, BridgeAgent's Zabbix and gnome-shell masquerade, the Medusa and REPTILE rootkits, and the hidden XOR-obfuscated credential file.
Sources
6 independent publishers whose own reporting we read for this story.
- bleepingcomputer.com
1 article · August 31, 2026
Chinese Fire Ant hackers turn Cisco routers into spying platforms
- scworld.comChina-linked campaign targets high-value networks, critical infrastructure
1 article · August 31, 2026
- securityaffairs.comChina-linked Fire Ant Hides Inside Trusted Infrastructure
1 article · August 31, 2026
- thecyberexpress.comChina-Linked Fire Ant Turned Cisco Routers, TACACS Servers Into Espionage Platforms
1 article · September 1, 2026
- thehackernews.comChina-Linked Fire Ant Hijacks Cisco Routers to Steal Credentials and Blind Security Logs
2 articles · August 31, 2026
- therecord.mediaChina's 'Fire Ant' campaign used compromised Cisco routers as platform for more attacks
1 article · September 1, 2026
Topics and entities
Topics
- Network Edge Device Security
- China-Nexus Cyber Espionage
- Authentication infrastructure