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

/

AI

/

September 3, 2026

Darktrace Advances Incident Investigation and AI-Agent Security with OpenAI Daybreak Models

Default blog imageDefault blog image

Earlier this year, Darktrace joined OpenAI’s Daybreak Defense Network to explore how their cyber capabilities can be integrated within Darktrace products and services to transform how security teams move from signal to action.

At the heart of this work is Darktrace's behavioral understanding of customer environments and identification of complex security incidents, combined with OpenAI models that can add context to help explain why an incident matters and its potential impact on the business. By bringing these capabilities into defensive workflows security teams already use, the goal is to give defenders not just greater visibility, but the context and guidance they need to act with confidence.

Since joining the program, we've been working with OpenAI to explore how these capabilities can address specific security challenges for defenders.

The problem we're solving

Attackers continue to change how they operate, including by using AI to increase the speed and scale of some techniques. Security teams are already managing a large volume of alerts, and the question isn't just what's happening, but how it could affect the organization. Even when an incident is fully investigated and correlated, technical severity alone doesn't tell a security team how much it actually matters to the business. That same challenge extends to internal AI adoption. As organizations adopt more AI systems and agents, security teams need visibility into their behavior, access and activity, along with the broader business context needed to identify and investigate potential risk.

Darktrace's Adaptive AI™ builds a detailed, organization-specific picture of what's normal for each environment, and uses that picture to investigate threats and identify complex security activity across domains. OpenAI's models can build on Darktrace's correlated, technically prioritized incidents by adding context that can help defenders understand what may be at stake.

What we're building

Our work is focused on two areas: supporting security investigation and response, and helping defenders identify risky behavior across enterprise AI systems and agents.

The first aligns Darktrace's behavioral understanding with OpenAI models to support  security investigation and prioritization. Darktrace's Adaptive AI continuously learns the unique patterns of normal behavior within each customer it protects, creating a deep, organization-specific understanding of its digital estate. When unusual activity emerges, OpenAI's models can draw on that context to help analysts investigate the incident, understand its significance and assess potential business consequences — reducing the need to manually assemble context from fragmented signals.

Second, we are exploring how these capabilities can support AI-agent and runtime security through Darktrace / SECURE AI™. OpenAI’s Daybreak models can build on the detections and visibility Darktrace / SECURE AI provides, connecting signals across a customer's environment and help defenders identify potentially risky behavior involving AI systems and agents. Activity that might appear isolated can instead be connected with related signals, helping defenders investigate the broader context and determine appropriate remediation.

Darktrace brings deep cybersecurity expertise, an evolving understanding of each customer's environment, and AI-driven identification of threats across the digital estate. Through the Daybreak Defense Network, Darktrace is exploring how OpenAI models can augment those capabilities in defensive security workflows — supporting incident investigation and response and improving visibility into AI-agent and runtime risk.

These capabilities are still in development, and we're excited to continue building on this work.

To learn more about how Darktrace continues to innovate to meet today's most pressing security challenges, register for our upcoming launch broadcast here.

Continue reading
About the author
Dr. Tim Bazalgette
Chief AI Officer, Darktrace

Blog

/

OT

/

September 3, 2026

Botnet Behind the Camera: Mirai Katana Activity on a Video Recording Device

Default blog imageDefault blog image

Key takeaways

  • Darktrace identified a camera device infected with the Mirai/Katana botnet in a sports-sector customer environment, showing how exposed IoT devices can become active participants in wider attack chains.
  • The compromise involved suspicious Wget behavior, file downloads from rare external IPs, unusual incoming HTTP connections to video recorder management interfaces, and large outbound data transfers to infrastructure associated with botnet activity.
  • The incident highlights the importance of extending visibility and response beyond traditional endpoints, as unmanaged or overlooked connected devices can be exploited for command-and-control, malware delivery, and data exfiltration.

Mirai and the Katana variant

Mirai is a botnet that first emerged in August 2016 and is well known for launching large-scale distributed-denial-of-service (DDoS) attacks, typically targeting exposed Internet of Things (IoT) devices. It identifies vulnerable IoT devices ,often by abusing default credentials or exposed services, and recruiting them into a remotely controlled botnet that can be used in DDoS campaigns [1].

Katana, one of the many variants that arose after Mirai’s source code was released publicly, was first observed in late 2020 and has been seen using more advanced capabilities, including custom command-and-control (C2), persistence mechanisms, and DDoS functionality [2].

In March 2026, research from the Nokia Deepfield Emergency Response Team (ERT) identified Katana as a Mirai-derived DDoS botnet targeting Android-based TV set-top boxes through exposed Android Debug Bridge (ADB) access.  Observed capabilities included custom C2, runtime domain rotation, multiple DDoS methods, and an on-device compiled kernel rootkit used for persistence and stealth [3].

Darktrace’s detection of Mirai Botnet activity on a camera device

In early 2026, Darktrace identified a Network/Digital Video Recorder (NVR/DVR) on the network of a sports-sector customer that had been infected with the Mirai Katana botnet and subsequently used to exfiltrate data from the customer’s environment. Seemingly related follow-up activity was observed on the same device several months later.

In both instances, the Darktrace Security Operations Centre (SOC) alerted the customer as part of the Managed Threat Detection (MTD) service. However, as Darktrace’s Autonomous Response capability was not fully enabled on the affected device, Darktrace was unable to proactively block the suspicious activity or prevent the compromise from continuing and recurring.

The initial compromise appears to have occurred when the affected device was seen using Wget to download Linux-based Executable and Linkable Format (ELF) files from a rare external IP, 195.177.94[.]105, which had not previously been observed in the customer’s network. Further analysis downloaded file hashes identified files related to the Mirai botnet.

Figure 1: Darktrace’s Real-Time AI Analyst investigation into the unusual outbound connection where the ELF files were downloaded.

Within a few hours, Darktrace detected the device uploading close to 3GB of data to another external IP, 50.7.49[.]4:3017 (ASN AS30058 FDCSERVERS), suggesting that the activity was likely routed via a virtual private server (VPS) hosted by FDC Servers [2]. Attackers often abuse VPS infrastructure from legitimate cloud providers to blend in with legitimate traffic and evade IP reputation and geolocation-based detections.

Figure 2:  Darktrace’s detection of the unusual data upload activity by the affected camera device.

Darktrace continued to observe similar data transfers to multiple rare endpoints  including 171.225.223[.]53, 95.161.128[.]62, 61.7.209[.]88, 95.161.128[.]62, which have been linked to Mirai by open-source intelligence (OSINT).

Figure 3: Darktrace’s detection of spikes in unusual external data transfer activity from the camera device.

Exploitation continued

Several months later, Darktrace identified the same exfiltration pattern on the device again, this time with stronger indications of associations with Mirai Katana botnet infection.

The device received incoming HTTP connections from 129.121.114[.]124, an external IP known to be associated with the Katana botnet IP [3]. The connections targeted the ‘/dvr/cmd’ path using the root username and user agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.246.

The ‘/dvr/cmd’ path appears to be associated with the affected device’s web management functionality. This API endpoint has historically been targeted by Mirai and other IoT botnets through the exploitation of critical command injection vulnerabilities and automated botnet exploitation [4].

Figure 4: Darktrace’s  detection of HTTP connectivity from the external IP associated with Mirai Katana Botnet.

A few days later, Darktrace observed the Wget utility being used to download ELF files, including “/lil”,  from the IP 129.121.114[.]124. OSINT reporting has since associated this IP address with the Mirai Katana botnet. Notably, the IP observed earlier in the year, 195.177.94[.]105, had also hosted a file named “lil”, indicating a link between the observed activity.

Over the following days, the device received a sudden spike in connections from multiple rare external endpoints, suggesting a possible successful brute force attack. Darktrace also observed the device exfiltrating just under 4GB of data to another Mirai-associated IP address,  66.92.198[.]194, over ports 3344, 954922, and 80. Finally, the device was seen uploading data to the Mirai botnet IP 5.175.249[.]53 over port138 and exhibited an increase in UDP connections to 34.18.28[.]10 over port 9068.

Following both file download events, Darktrace identified spikes in external data transfers and connection attempts to rare destinations. While Darktrace’s Threat Research team could not confirm with high confidence that this to activity was directly associated with Mirai, it may indicate that Mirai Katana includes data exfiltration functionality.

Darktrace’s threat researchers also identified an internet-facing NTP server belonging to a separate customer receiving incoming connection attempts from the same initially observed IP, 195.177.94[.]105,over the port 123. This suggests that Mirai Katana may not exclusively target IoT devices.

Conclusion

This case demonstrates how threat actors can exploit overlooked IoT and OT devices to support broader malicious objectives. Here, a camera device infected with a botnet was used to exfiltrate data from the customer's environment, showing how peripheral assets can become active participants in an attack chain.

This case also reinforces a challenge many organizations face today: extending security visibility beyond traditional endpoints and servers. Cameras, sensors, and other connected devices often operate with limited monitoring and may fall outside established security processes, despite maintaining network connectivity and access to potentially sensitive environments. This is particularly relevant in the sports sector, where growing reliance on connected cameras, smart stadium technologies, and other IoT devices continues to expand the attack surface, as highlighted in Darktrace's Sports Sector Threat Report.

As botnets like Kata and Mirai continue to evolve, defenders need visibility across unmanaged IoT and edge devices, as well as security solutions that can recognize subtle deviations in device behavior that may indicate an emerging compromise.

Credit to Parvatha Ananthakannan (Cyber Analyst), Signe Zaharka (Principal Analyst)

Edited by Ryan Traill (Content Manager)

Appendices

Darktrace Model Detections

·      Anomalous File / EXE from Rare External Location

·      Anomalous File / Multiple EXE from Rare External Locations

·      Device / Initial Attack Chain Activity

·      Unusual Activity / Unusual External Data to New Endpoint

·      Anomalous Connection / Data Sent to Rare Domain

·      Unusual Activity / Enhanced Unusual External Data Transfer

·      Anomalous Connection / Uncommon 1 GiB Outbound

·      Device / Significant UDP Increase

·      Anomalous Connection / Low and Slow Exfiltration to IP

·      Compromise / Large Number of Suspicious Failed Connections

·      Compromise / Large Number of Suspicious Successful Connections

·      Unusual Activity / Unusual External Activity

·      Compliance / SSH to Rare External Destination

·      Unusual Activity / Unusual DNS

·      Device / External Network Scan

·      Device / Suspicious DNS Activity

·      Device / Large Number of Model Alerts

List of Indicators of Compromise (IoCs)

Indicator of Compromise Type Description
195.177.94[.]105 IP C2 endpoint
50.7.49[.]4:30171 IP Possible C2 endpoint
129.121.114[.]124 IP C2 endpoint
hxxp://195.177.94[.]105/n3 URL Likely C2 endpoint
hxxp://195.177.94[.]105/n2 URL Likely C2 endpoint
hxxp://129.121.114[.]124/lil URL Likely C2 endpoint
hxxp://129.121.114[.]124/HHn URL Possible C2 endpoint
hxxp://129.121.114[.]124/JFc URL Possible C2 endpoint
hxxp://129.121.114[.]124/jum URL Likely C2 endpoint
hxxp://129.121.114[.]124/OaSf URL Likely C2 endpoint
hxxp://129.121.114[.]124/OPWg URL Possible C2 endpoint
hxxp://129.121.114[.]124/vHwK URL Possible C2 endpoint
hxxp://129.121.114[.]124/VLv URL Possible C2 endpoint
hxxp://129.121.114[.]124/WbJ URL Possible C2 endpoint
hxxp://129.121.114[.]124/zkR URL Possible C2 endpoint
Ab17883ae4c3bc6afa18c439166eeeb4b03186e3093d984e3a95f573e0fcb7d8 SHA-256 Mirai payload
3d587e809dac49d34a3f717e072fd0aebe5e71db63333e45c81577d6b4266f87 SHA-256 Mirai payload
Bf6e81733a7e209d3dce80d15bf3c5d300752d961fae6b45d90c9bbe7f8c89a2 SHA-256 Possible payload
f25488303813ab1ec0eaa71562938601aac185e8aaf93adb84522557f7cf4dd6 SHA-256 Possible payload
0cb4ff6b71f4423184bfa35c34e9090297637208b0e30205d4b224e56abde2ef SHA-256 Possible payload
19c24cbeaf06b2e7697083f33a85521a9315105c784691bde7420fde4cc69410 SHA-256 Likely Mirai payload
1e74f734fff8df91f4f7172d0de10c421eca78aeb800e8a48e16bc5dbde5d20e SHA-256 Possible payload
6e71f7763d1f29d5712106ebb122e281c32787540aa2342b0fe5351d585d18d7 SHA-256 Possible payload
71f4ff7cdb6d6a7d2673c543c5d2535093afbd707b20a5b9ddf735466c1105c1 SHA-256 Possible payload
76db7ee73ebf15e48a3cb24a074d92248671ef2c6ed3bc3e708377341fb7674d SHA-256 Possible payload
da87a65f7beb438e61f0b61964fed8aa305a380f569042f84c55eca8fa7929b8 SHA-256 Possible payload
e15809eb6ba66477175270d62cfa53e4bf278595f69938708c81c4bc457930fe SHA-256 Mirai payload

MITRE ATT&CK Mapping

Tactic Technique ID Technique / Sub-technique
Initial Access T1659 Content Injection
T1189 Drive-by Compromise
Exfiltration T1041 Exfiltration Over C2 Channel
T1048.003 Exfiltration Over Unencrypted Non-C2 Protocol
Command and Control T1105 Ingress Tool Transfer
T1095 Non-Application Layer Protocol
T1571 Non-Standard Port
Reconnaissance T1595.001 Scanning IP Blocks
Continue reading
About the author
Parvatha Ananthakannan
Cyber Analyst
Your data. Our AI.
Elevate your network security with Darktrace AI