UAT-12643 Solana C2 is the route Cisco Talos described in its November 18, 2026, research discussion. Talos says the Overlord remote access trojan reads encrypted server information from Solana transaction memos. Defenders should review suspicious endpoint behavior and its related blockchain requests together.
Talos characterizes UAT-12643 as a suspected North Korea-aligned actor. That is the research team’s assessment, not a confirmed identity. Its discussion describes malware behavior but does not establish an affected organization or a current incident in a reader’s environment.
How Does UAT-12643 Solana C2 Work?
Talos says the actor placed encoded or encrypted routing information in Solana transaction memos. The Overlord RAT then retrieves relevant transaction history, decodes the information, and uses the resulting server address for its next connection. The chain acts as a durable address directory rather than the final malware server.
This design lets an operator change the address the malware retrieves without replacing the implant, according to Talos. A blocked server can therefore be followed by another address in later on-chain data. The command and control (C2) model still includes an endpoint connecting to a server.
Talos describes this as one example of abusing public blockchains for resilient malware routing. The chain’s legitimate use means a connection to blockchain infrastructure alone does not identify this campaign. A cyber threat intelligence program should connect the network observation to the process that initiated it.
What Should Defenders Check First?
Start with endpoints that make unexpected requests to blockchain RPC services, then inspect which process made them. Talos advises looking for malware behavior near the endpoint, including memory activity and host-level API calls. Correlate those findings with subsequent outbound connections and the process’s normal role.
- Identify the processFind the process responsible for unexpected blockchain requests.
- Check its behaviorReview execution history, memory findings, and host-level API activity.
- Correlate connectionsCompare requests with later outbound connections from the same process.
- Preserve evidenceKeep endpoint and network records for the incident team before containment.
This sequence is our defensive reading of Talos’s observations, not a signature for every Solana user. Authorized finance tools can also query public chains. Apply the organization’s approved software inventory and business context before treating a request as malicious.
Why Is a Domain Block Alone Insufficient?
Talos explains that a blockchain dead drop can remain available after a particular server is blocked. A domain block may interrupt one connection while the implant retrieves a replacement address. Containment should therefore focus on the suspicious process and host as well as any known server.
Review egress records for requests followed by unusual connections, then validate the endpoint evidence. A threat hunting workflow can make the process, request, and follow-on connection a single case. This approach helps avoid classifying all blockchain traffic as hostile.
How Much Does Discussion Volume Tell Us?
Brandefense Blackhole counted 497 dark-chat posts matching the broad term “Talos” from August 20 through November 18, 2026. The measured unit is a post containing that researcher name, not a UAT-12643 mention or verified incident. Do not use that volume to infer campaign scale.
The operational signal here comes from Talos’s malware analysis and local endpoint evidence. Its podcast does not provide a confirmed victim count or an ATT&CK mapping for this example. Preserve those limits when prioritizing response and explaining the case internally.
Frequently Asked Questions
Does Solana traffic alone prove Overlord RAT infection?
No. Talos describes a malware use of Solana memos, but legitimate applications also query the chain. Check the initiating process and its behavior.
What is the first useful investigation step?
Identify the endpoint process behind unexpected blockchain RPC requests. Correlate its execution and later outbound connections with endpoint findings.
Is the North Korea link confirmed?
Talos describes UAT-12643 as suspected North Korea-aligned. Treat that as a research assessment rather than a confirmed actor identity.
