October 25, 2016 By Larry Loeb < 1 min read

The Sphinx Trojan is based on the source code of the infamous Zeus banking Trojan. First seen around August 2015, Sphinx has been upgraded with a new method of randomizing the domain names it uses for the command-and-control (C&C) servers to which it links.

Besides the primary domains of the C&C servers hardcoded into the Trojan, this kind of approach is designed to implement a backup method should authorities take down the primary servers.

A Simplistic Algorithm

This Domain Generation Algorithm (DGA) enables the attacker to establish non-hardcoded C&C servers and obtain domain names that only he or she knows beforehand. The malware author can then register these names for nefarious use. Many pieces of malware use DGAs to generate C&C host names. That goes for both primary and backup servers.

Arbor Networks classified this DGA as time-dependent, deterministic and arithmetic-based (TDD-A). It uses the current date as the initial seed, creates random strings of 16 characters and appends .com at the end.

The DGA generates 128 domains per day, according to Softpedia. But researchers had no problem cracking this simplistic algorithm. They even revealed the code used to figure out the domains.

Sphinx Trojan Gets Cracked

Once the researchers figured out the technique, they set up sinkholes for the Trojan. The sinkholes found only 1,230 active bots, far fewer than the millions they had assumed were out in the wild.

According to Arbor Networks, most of the bots were located in Brazil That makes sense, since an IBM X-Force report in August found that Sphinx had been used in a Brazilian bank campaign.

Now that the DGA has been cracked, authorities should be able to set up a way to track the Trojan and stop its criminal activity.

More from

FYSA — VMware Critical Vulnerabilities Patched

< 1 min read - SummaryBroadcom has released a security bulletin, VMSA-2025-0004, addressing and remediating three vulnerabilities that, if exploited, could lead to system compromise. Products affected include vCenter Server, vRealize Operations Manager, and vCloud Director.Threat TopographyThreat Type: Critical VulnerabilitiesIndustry: VirtualizationGeolocation: GlobalOverviewX-Force Incident Command is monitoring activity surrounding Broadcom’s Security Bulletin (VMSA-2025-0004) for three potentially critical vulnerabilities in VMware products. These vulnerabilities, identified as CVE-2025-22224, CVE-2025-22225, and CVE-2025-22226, have reportedly been exploited in attacks. X-Force has not been able to validate those claims. The vulnerabilities…

SoaPy: Stealthy enumeration of Active Directory environments through ADWS

10 min read - Introduction Over time, both targeted and large-scale enumeration of Active Directory (AD) environments have become increasingly detected due to modern defensive solutions. During our internship at X-Force Red this past summer, we noticed FalconForce’s SOAPHound was becoming popular for enumerating Active Directory environments. This tool brought a new perspective to Active Directory enumeration by performing collection via Active Directory Web Services (ADWS) instead of directly through Lightweight Directory Access Protocol (LDAP) as other AD enumeration tools had in the past.…

Smoltalk: RCE in open source agents

26 min read - Big shoutout to Hugging Face and the smolagents team for their cooperation and quick turnaround for a fix! Introduction Recently, I have been working on a side project to automate some pentest reconnaissance with AI agents. Just after I started this project, Hugging Face announced the release of smolagents, a lightweight framework for building AI agents that implements the methodology described in the ReAct paper, emphasizing reasoning through iterative decision-making. Interestingly, smolagents enables agents to reason and act by generating…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today