Blog
/
Network
/
April 26, 2023

Gozi ISFB Malware Detection Insights and Analysis

Uncover how Gozi ISFB operates and how Darktrace’s detection capabilities help secure your systems against this versatile malware.
Inside the SOC
Darktrace cyber analysts are world-class experts in threat intelligence, threat hunting and incident response, and provide 24/7 SOC support to thousands of Darktrace customers around the globe. Inside the SOC is exclusively authored by these experts, providing analysis of cyber incidents and threat trends, based on real-world experience in the field.
Written by
Justin Torres
Cyber Analyst
Default blog image
26
Apr 2023

Mirroring the overall growth of the cybersecurity landscape and the advancement of security tool capabilities, threat actors are continuously forced to keep pace. Today, threat actors are bringing novel malware into the wild, creating new attack vectors, and finding ways to avoid the detection of security tools. 

One notable example of a constantly adapting type of malware can be seen with banking trojans, a type of malware designed to steal confidential information, such as banking credentials, used by attackers for financial gain. Gozi-ISFB is a widespread banking trojan that has previously been referred to as ‘the malware with a thousand faces’ and, as it name might suggest, has been known under various names such as Gozi, Ursnif, Papras and Rovnix to list a few.

Between November 2022 and January 2023, a rise in Gozi-ISFB malware related activity was observed across Darktrace customer environments and was investigated by the Darktrace Threat Research team. Leveraging its Self-Learning AI, Darktrace was able to identify activity related to this banking trojan, regardless of the attack vectors or delivery methods utilized by threat actors.

We have moderate to high confidence that the series of activities observed is associated with Gozi-ISFB malware and high confidence in the indicators of compromise identified which are related to the post-compromise activities from Gozi-ISFB malware. 

Gozi-ISFB Background

The Gozi-ISFB malware was first observed in 2011, stemming from the source code of another family of malware, Gozi v1, which in turn borrowed source code from the Ursnif malware strain.  

Typically, the initial access payloads of Gozi-ISFB would require an endpoint to enable a macro on their device, subsequently allowing a pre-compiled executable file (.exe) to be gathered from an attacker-controlled server, and later executed on the target device.

However, researchers have recently observed Gozi-ISFB actors using additional and more advanced capabilities to gain access to organizations networks. These capabilities range from credential harvest, surveilling user keystrokes, diverting browser traffic from banking websites, remote desktop access, and the use of domain generation algorithms (DGA) to create command-and-control (C2) domains to avoid the detection and blocking of traditional security tools. 

Ultimately, the goal of Gozi-ISFB malware is to gather confidential information from infected devices by connecting to C2 servers and installing additional malware modules on the network. 

Darktrace Coverage of Gozi-ISFB 

Unlike traditional security approaches, Darktrace DETECT/Network™ can identify malicious activity because Darktrace models build an understanding of a device’s usual pattern of behavior, rather than using a static list of indicators of compromise (IoCs) or rules and signatures. As such, Darktrace is able to instantly detect compromised devices that deviate from their expected behavioral patterns, engaging in activity such as unusual SMB connections or connecting to newly created malicious endpoints or C2 infrastructure. In the event that Darktrace detects malicious activity, it would automatically trigger an alert, notifying the customer of an ongoing security concern. 

Regarding the Gozi-ISFB attack process, initial attack vectors commonly include targeted phishing campaigns, where the recipient would receive an email with an attached Microsoft Office document containing macros or a Zip archive file. Darktrace frequently observes malicious emails like this across the customer base and is able to autonomously detect and action them using Darktrace/Email™. In the following cases, the clients who had Darktrace/Email did not have evidence of compromise through their corporate email infrastructure, suggesting devices were likely compromised via the access of personal email accounts. In other cases, the customers did not have Darktrace/Email enabled on their networks.

Upon downloading and opening the malicious attachment included in the phishing email, the payload subsequently downloads an additional .exe or dynamic link library (DLL) onto the device. Following this download, the malware will ultimately begin to collect sensitive data from the infected device, before exfiltrating it to the C2 server associated with Gozi-ISFB. Darktrace was able to demonstrate and detect the retrieval of Gozi-ISFB malware, as well as subsequent malicious communication on multiple customer environments. 

In some attack chains observed, the infected device made SMB connections to the rare external endpoint ’62.173.138[.]28’ via port 445. Darktrace recognized that the device used unusual credentials for this destination endpoint and further identified it performing SMB reads on the share ‘\\62.173.138[.]28\Agenzia’. Darktrace also observed that the device downloaded the executable file ‘entrat.exe’ from this connection as can be seen in Figure 1.

Figure 1: Model breach event log showing an infected device making SMB read actions on the share ‘\\62.173.138[.]28\Agenzia’. Darktrace observed the device downloading the executable file ‘entrat.exe’ from this connection.

Subsequently, the device performed a separate SMB login to the same external endpoint using a credential identical to the device's name. Shortly after, the device performed a SMB directory query from the root share drive for the file path to the same endpoint. 

Figure 2:SMB directory query from the root share drive for the file path to the same endpoint, ’62.173.138[.]28’.

In Gozi-ISFB compromises investigated by the Threat Research team, Darktrace commonly observed model breaches for ‘Multiple HTTP POSTs to Rare Hostname’ and the use of the Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 10.0; Win64; x64)’ user agent. 

Devices were additionally observed making external connections over port 80 (TCP, HTTP) to endpoints associated with Gozi-ISFB. Regarding these connections, C2 communication was observed used configurations of URI path and resource file extension that claimed to be related to images within connections that were actually GET or POST request URIs. This is a commonly used tactic by threat actors to go under the radar and evade the detection of security teams.  

An example of this type of masqueraded URI can be seen below:

In another similar example investigated by the Threat Research team, Darktrace detected similar external connectivity associated with Gozi-ISFB malware. In this case, DETECT identified external connections to two separate hostnames, namely ‘gameindikdowd[.]ru’ and ‘jhgfdlkjhaoiu[.]su’,  both of which have been associated to Gozi-ISFB by OSINT sources. This specific detection included HTTP beaconing connections to endpoint, gameindikdowd[.]ru .

Details observed from this event: 

Destination IP: 134.0.118[.]203

Destination port: 80

ASN: AS197695 Domain names registrar REG.RU, Ltd

User agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 10.0; Win64; x64

The same device later made anomalous HTTP POST requests to a known Gozi-ISFB endpoint, jhgfdlkjhaoiu[.]su. 

Details observed:

Destination port: 80

ASN: AS197695 Domain names registrar REG.RU, Ltd

User agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 10.0; Win64; x64

Figure 3: Packet Capture (PCAP) with the device conducting anomalous HTTP POST requests to a Gozi-ISFB related IOC, ‘jhgfdlkjhaoiu[.]su’.

Conclusions 

With constantly changing attack infrastructure and new methods of exploitation tested and leveraged hour upon hour, it is critical for security teams to employ tools that help them stay ahead of the curve to avoid critical damage from compromise.  

Faced with a notoriously adaptive malware strain like Gozi-ISFB, Darktrace demonstrated its ability to autonomously detect malicious activity based upon more than just known IoCs and attack vectors. Despite the multitude of different attack vectors utilized by threat actors, Darktrace was able to detect Gozi-ISFB activity at various stages of the kill chain using its anomaly-based detection to identify unusual activity or deviations from normal patterns of life. Using its Self-Learning AI, Darktrace successfully identified infected devices and brought them to the immediate attention of customer security teams, ultimately preventing infections from leading to further compromise.  

The Darktrace suite of products, including DETECT/Network, is uniquely placed to offer customers an unrivaled level of network security that can autonomously identify and respond to arising threats against their networks in real time, preventing suspicious activity from leading to damaging network compromises.

Credit to: Paul Jennings, Principal Analyst Consultant and the Threat Research Team

Appendices

List of IOCs

134.0.118[.]203 - IP Address - Gozi-ISFB C2 Endpoint

62.173.138[.]28 - IP Address - Gozi-ISFB  C2 Endpoint

45.130.147[.]89 - IP Address - Gozi-ISFB  C2 Endpoint

94.198.54[.]97 - IP Address - Gozi-ISFB C2 Endpoint

91.241.93[.]111 - IP Address - Gozi-ISFB  C2 Endpoint

89.108.76[.]56 - IP Address - Gozi-ISFB  C2 Endpoint

87.106.18[.]141 - IP Address - Gozi-ISFB  C2 Endpoint

35.205.61[.]67 - IP Address - Gozi-ISFB  C2 Endpoint

91.241.93[.]98 - IP Address - Gozi-ISFB  C2 Endpoint

62.173.147[.]64 - IP Address - Gozi-ISFB C2 Endpoint

146.70.113[.]161 - IP Address - Gozi-ISFB  C2 Endpoint 

iujdhsndjfks[.]ru - Hostname - Gozi-ISFB C2 Hostname

reggy505[.]ru - Hostname - Gozi-ISFB  C2 Hostname

apr[.]intoolkom[.]at - Hostname - Gozi-ISFB  C2 Hostname

jhgfdlkjhaoiu[.]su - Hostname - Gozi-ISFB  C2 Hostname

gameindikdowd[.]ru - Hostname - Gozi-ISFB  Hostname

chnkdgpopupser[.]at - Hostname – Gozi-ISFB C2 Hostname

denterdrigx[.]com - Hostname – Gozi-ISFB C2 Hostname

entrat.exe - Filename – Gozi-ISFB Related Filename

Darktrace Model Coverage

Anomalous Connection / Multiple HTTP POSTs to Rare Hostname

Anomalous Connection / Posting HTTP to IP Without Hostname

Anomalous Connection / New User Agent to IP Without Hostname

Compromise / Agent Beacon (Medium Period)

Anomalous File / Application File Read from Rare Endpoint

Device / Suspicious Domain

Mitre Attack and Mapping

Tactic: Application Layer Protocol: Web Protocols

Technique: T1071.001

Tactic: Drive-by Compromise

Technique: T1189

Tactic: Phishing: Spearphishing Link

Technique: T1566.002

Model Detection

Anomalous Connection / Multiple HTTP POSTs to Rare Hostname - T1071.001

Anomalous Connection / Posting HTTP to IP Without Hostname - T1071.001

Anomalous Connection / New User Agent to IP Without Hostname - T1071.001

Compromise / Agent Beacon (Medium Period) - T1071.001

Anomalous File / Application File Read from Rare Endpoint - N/A

Device / Suspicious Domain - T1189, T1566.002

References

https://threatfox.abuse.ch/browse/malware/win.isfb/

https://www.cisa.gov/news-events/cybersecurity-advisories/aa22-216a

https://www.fortinet.com/blog/threat-research/new-variant-of-ursnif-continuously-targeting-italy#:~:text=Ursnif%20(also%20known%20as%20Gozi,Italy%20over%20the%20past%20year

https://medium.com/csis-techblog/chapter-1-from-gozi-to-isfb-the-history-of-a-mythical-malware-family-82e592577fef

Inside the SOC
Darktrace cyber analysts are world-class experts in threat intelligence, threat hunting and incident response, and provide 24/7 SOC support to thousands of Darktrace customers around the globe. Inside the SOC is exclusively authored by these experts, providing analysis of cyber incidents and threat trends, based on real-world experience in the field.
Written by
Justin Torres
Cyber Analyst

More in this series

No items found.

Blog

/

Email

/

July 24, 2026

Darktrace / EMAIL Expands Behavioral Defense Across Email and Collaboration Workflows

Default blog imageDefault blog image

Email and collaboration tools do more than carry messages. They are where organizations approve payments, share sensitive data, reset credentials, and make thousands of everyday decisions. Increasingly, they are interfaces through which humans direct AI agents in their daily activity. Email, Slack and Teams are high volume, rich with sensitive data, and an easy place to hide malicious activity.

The opportunity isn’t lost on bad actors. Darktrace / EMAIL detected more than 32 million high-confidence phishing emails globally in 2025, and 70% of those messages passed DMARC authentication.  Phishing is increasingly difficult to detect and familiar trust signals alone are not enough. People and security teams need to understand how a message fits the normal behavior of the sender, recipient, and organization. They also need to correlate activity across platforms to spot threats that span multiple channels.

To effectively secure against today’s evolved threats, security teams need to act at two levels: they need to help each employee make a safer decision ‘in the moment’, and they need to understand the wider patterns that may expose the business to risk.

Darktrace is introducing four new capabilities in Darktrace / EMAIL to address both challenges. The new features explain suspicious content more clearly to end users, strengthen the capabilities of Darktrace / Adaptive Human Defense with richer guidance, let organizations define their own patterns for detecting sensitive data in messages, and give security teams a process-level view of risk across email and collaboration workflows.

Darktrace / EMAIL Inbox Analysis highlights risky content within your emails

A warning is more useful when it explains what the user should look at. To help do that, we’ve expanded Darktrace / EMAIL’s Inbox Analysis Add-In to highlight potentially dangerous content within the body of emails that Darktrace / EMAIL flags as potentially suspicious or high risk.  

The add-in can highlight language designed to create urgency, financial references, requests for payment, suspicious links, and content that is unusual for the sender. Each highlighted element includes a pop up that explains why it may be suspicious. Instead of asking an employee to accept a verdict without context, the analysis helps them examine the message and make a more informed decision.

Enhanced Just-In-Time Training Banners in Darktrace / Adaptive Human Defense

Enhanced Just-In-Time Training Banners build on the same principle. The banners now include a contextual header, actionable advice, and specific detection context. This gives employees more useful guidance at the point of risk without adding unnecessary information or cognitive load.

Together, the capabilities help turn a warning into a short learning moment. Employees can see what looks unusual, understand what action to take, and build their judgment.

Custom Sensitive Data Detection in Darktrace / EMAIL - Data Loss Prevention

Sensitive data is different for every business. Standard categories such as payment card details or government identifiers matter, but organizations also have their own customer codes, project names, research formats, account structures, and internal identifiers.

Custom Sensitive Data Detection in Darktrace / EMAIL - Data Loss Prevention allows administrators to write custom expressions for the data their organization needs to protect. Matched content can trigger existing model actions and data loss prevention (DLP) workflows, extending Darktrace's DLP capabilities.

This extends data loss detection beyond a fixed library of common data types. Security teams can apply controls to information that is sensitive in the context of their own organization and adapt those controls as the business changes.

Introducing Email and Collaboration Workflow Risk Posture Dashboards

Some of the most important risks are not isolated events. They are repeated ways of working that create an opening for error, misuse, or attack. For example, a payment request may be one suspicious message, but a recurring approval workflow that relies on weak verification is a business process risk.

The new Email and Collaboration Workflow Risk Posture Dashboard analyzes email and collaboration data across Email, Microsoft Teams, Slack and Zoom to provide a process-level view of risk in the organization. These may include financial authorization workflows, sensitive data sharing patterns, and activity that could expose credentials.

The dashboard brings these patterns into a view and provides actionable recommendations. This helps security teams determine where to investigate or strengthen controls, where ownership needs to be clarified, and where the business may need to change a risky process. It gives CISOs a clearer view of how human and communication risk is embedded in everyday operations, not only where individual alerts occur.

Behavior connects the individual decision to the wider risk

These capabilities build on Darktrace’s unique behavioral approach to security. We use Adaptive AI to learn how people and AI normally behave within an organization, creating the context needed to recognize when activity changes.

Within the Darktrace Behavioral Defense Platform, Darktrace / EMAIL helps protect people against phishing, account takeover, data exfiltration, and human risk across email and collaboration tools. The new capabilities extend that protection in both directions. They give employees clearer context for the decision in front of them, while giving security leaders a broader view of the workflows and behavior that create risk across the organization.

The result is not simply more alerts. It is a better understanding of why something is risky, what action to take, and where the organization can reduce risk before a familiar process becomes an easy route for an attacker.

[related-resource]

Continue reading
About the author
Carlos Gray
Senior Product Marketing Manager, Email

Blog

/

AI

/

July 24, 2026

When Guardrails Break: Why Securing AI Requires Behavioral Detection and Autonomous Containment

behavioral detectionDefault blog imageDefault blog image

Bottom line up front: Governance, guardrails, identity controls, and secure development are necessary to secure AI, but they are not sufficient. AI systems are probabilistic, adaptive, and non-deterministic. Therefore, organizations need two additional layers of security:

  1. Behavioral-based detection that can identify when AI begins to act outside its intended purpose; and  
  2. Surgical, explainable autonomous containment that can stop risky activity before it causes material damage.  

That capability depends on multiple specialized AI models working together, not one LLM making every decision.

Organizations are embedding AI into development, business operations, and security workflows faster than most security programs can adapt. The risk is no longer limited to the model. It extends across prompts, data, identities, agents, memory, APIs, tools, permissions, and the trust relationships connecting them.

In my recent blog, Securing AI: Analysis of the Complete Security Stack with Governance and Controls, I outlined a defense-in-depth strategy spanning governance, identity, data security, secure development, runtime detection, autonomous containment, and recovery. The most urgent requirement across that architecture is the ability to understand how AI behaves in practice and contain it when that behavior becomes risky.  

Why non-deterministic systems require behavioral-based detection

Traditional controls remain foundational. Organizations need least privilege, strong identity controls, secure-by-design architecture, data governance, AI inventories, guardrails, testing, and clear boundaries on autonomy.

But deterministic controls, which assume predictable and repeatable behavior, cannot fully secure non-deterministic systems, where the same input may not always produce the same outcome.

AI agents can interpret the same instruction differently, chain individually authorized actions into an unsafe outcome, or pursue a legitimate goal through a method the organization did not anticipate. One of the most recent examples of this is the incident that OpenAI and Hugging Face jointly disclosed, where an autonomous agent escaped its intended testing boundaries and compromised Hugging Face infrastructure.  

An agent may have permission to access data and invoke a tool, but that does not mean every use of that access is appropriate. It is not enough to know whether an action is allowed. Organizations need to know whether it makes sense.

  • Is this normal for this agent?  
  • Is it acting within its intended purpose?  
  • Is it accessing unusual data, invoking an unexpected tool, or beginning to drift?  
  • Do a series of ordinary-looking actions become risky when viewed together?

Behavioral-based detection specific to an environment or organization with an understanding of context and risk enables provides the needed detection engineering for AI systems. It learns normal activity across people, systems, data, devices, and AI agents, then identifies deviations and evaluates their risk, intent, and context. This enables detection of misuse, abuse, compromise, manipulation, and unintended behavior even when no known attack signature or explicit policy violation exists.

Why accuracy is the foundation for SOC optimization

AI will only improve the SOC if it produces accurate, explainable, and actionable outcomes.

If analysts must manually validate every AI-generated finding because they cannot understand the evidence or confidence behind it, automation has not reduced workload. It has moved the workload. False positives increase fatigue. False negatives cause the most risk and damage to organizations. Inaccurate autonomous actions can disrupt critical operations.

Accuracy is therefore more than a model-performance metric. It is the prerequisite for analyst trust, SOC optimization, and safe autonomous response.

That accuracy is unlikely to come from one model.

Generative AI is valuable for natural-language analysis, summarization, and human interaction. But an LLM should not be the sole analytical engine for behavioral-based detection, investigation, risk assessment, and containment. Interpretability and consistency are required for high-consequence security decisions.

A stronger architecture uses multiple specialized AI systems collaboratively:  

  • Behavioral models can establish normal activity.  
  • Unsupervised learning can identify novel anomalies.  
  • Graph analysis can evaluate relationships among agents, identities, systems, and tools.  
  • Other models can correlate events, investigate competing hypotheses, and assess risk.  
  • Semantic models can analyze language where behavior-based language analysis is needed but this can be used in tandem with vector embeddings, graph neural networks, and a variety of other AI systems.

Each model contributes a different analytical perspective. Their outputs can corroborate one another, improving accuracy and creating a more reliable basis for response. The objective is not one model operating as an oracle. It is layered, adaptive intelligence designed to produce decisions the SOC can understand and trust.

Autonomous containment is required to secure autonomous systems

Many SOCs remain hesitant to trust LLM-based agents with autonomous containment. That concern is reasonable. A poorly selected response can isolate the wrong asset, stop a critical workflow, block a legitimate identity, or create more operational damage than the original incident.

But relying exclusively on human response is also not viable.

AI systems can operate at machine speed. They can expose sensitive data, execute workflows, modify records, call tools, or propagate actions across connected systems before an analyst can investigate and intervene. The behavior may be unintentional, the result of an agent optimizing toward a goal, or caused by misuse, compromise, prompt injection, or offensive AI.

Intent affects the investigation. It does not change the need to stop the damage.

Organizations need autonomous response, but it must be surgical and explainable. The objective is not to shut down an entire agent, user, application, or business process whenever an anomaly occurs. It is to interrupt the specific risky behavior: block an unusual connection, constrain a tool call, stop an abnormal data transfer, or temporarily limit an agent when it is performing anomalous, risky activity.  

That buys humans time. It stops the spread, limits damage, and allows the SOC to investigate without unnecessarily disrupting the business.

Layered, Adaptive AI provides a path forward

Darktrace has spent more than a decade researching and operationalizing layered, behavioral, Adaptive AI that learns a specific organization rather than relying only on historic attacks or predefined signatures.

The approach is designed to understand normal behavior, identify anomalous activity, assess its risk, correlate related events, autonomously investigate, and, when necessary, apply targeted containment while normal operations continue.

That sequence matters. Autonomous response cannot simply be added to the end of an LLM workflow. Trusted containment depends on broad visibility, continuous behavioral understanding, multiple analytical techniques, risk and context evaluation, autonomous investigation, explainability, and precise response actions.

This represents a more responsible model for security autonomy: not automation for its own sake, but controlled autonomy built to improve security outcomes and protect business operations.

Security must enable AI adoption

The answer for security teams is not to block AI. Organizations are adopting it to improve productivity, accelerate development, and create new business value.

But innovation without behavioral detection and autonomous containment is not sustainable.

Organizations should continue investing in governance, identity, least privilege, data security, secure MLOps, guardrails, testing, evaluation, validation, verification, kill switches, rollback, and forensic readiness. At the same time, they cannot wait for every governance program to mature before addressing runtime risk.

Behavioral-based detection and autonomous containment provide an immediate layer of resilience. They allow organizations to detect exploitation and risky AI behavior they did not anticipate, contain it at machine speed, and preserve human control over broader remediation.

The future of AI security will not be defined by a single model making every decision. It will be defined by multiple specialized AI systems working collaboratively, with sufficient accuracy, transparency, and context to support trusted autonomous action.

Surgical, explainable autonomous containment is no longer a future capability. It is a requirement for scaling AI securely today.

Learn how to build a defense-in-depth strategy for securing AI at scale in our talk at Black Hat on August 5 at 3:15 PM.  

[related-resource]

Continue reading
About the author
Nicole Carignan
SVP, Security & AI Strategy, Field CISO
Your data. Our AI.
Elevate your network security with Darktrace AI