Blog
/
/
July 7, 2020

Cryptomining Campaigns & Technical Analysis of Vulnerability

Crypto-mining campaigns stood no chance against Darktrace's AI as it identified the threat in real time. Put your trust in Darktrace's assistance!
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
Max Heinemeyer
Global Field CISO
Default blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog image
07
Jul 2020

Introduction

The speed with which attackers can weaponize vulnerabilities is steadily increasing. While technology is rapidly evolving and cyber-attacks are becoming more sophisticated, the advantages of exploiting software vulnerabilities over devising a more elaborate and lengthy attack plan have not been overlooked by hackers. These vulnerabilities are also a quick way to gain access into a businesses’ infrastructure. In recent years, attackers have found great benefit and substantial success through quickly weaponizing vulnerabilities in web-facing systems.

Just recently, critical vulnerabilities in Citrix Gateway resulted in a spate of activity targeting Darktrace customers, as reported earlier this year. Without an immediate patch released upon the public announcement of the discovered flaws in Citrix, exploits quickly followed. Similarly, in late April, SaltStack developers reported vulnerabilities in Salt, an open source framework used to monitor and update the state of servers in cloud environments and data centers.

The vulnerabilities found in Salt would allow hackers to bypass authentication and authorization controls and execute code in Salt master servers exposed to the internet. The Salt master is responsible for sending commands to Salt minions and can manage thousands of minions at once. Due to this structure, one exposed Salt master can lead to a compromise of all underlying minions.

On May 2, Darktrace detected successful crypto-miner infections across a number of its customers exploiting the CVE-2020-11651 and CVE-2020-11652 vulnerabilities in SaltStack server management software. In the same weekend, LineageOS — an Android mobile operating system – and Ghost — a blogging platform – both reported suffering a crypto-mining attack due to exposed, unpatched Salt servers. Most notable about these attacks was the sheer speed from a vulnerability being published to a widespread attack campaign.

Timeline

Figure 1: A timeline of events identified by Darktrace on May 3

Technical analysis

Initial compromise

Darktrace initially detected that a number of customer servers running SaltStack were making external connections to endpoints previously not seen on the network. The connections used the curl or wget utilities to download and execute a bash script, which would install a secondary-stage payload containing a cryptocurrency miner.

The systems were targeted directly utilizing 2020-11651 and CVE-2020-11652 vulnerabilities in the ZeroMQ protocol running on SaltStack. These vulnerabilities would allow direct remote code execution as root on the targeted systems, allowing the script to be downloaded and executed successfully with highest system privileges.

The downloader script is almost identical to the one utilized in March in H2Miner infections targeting exposed Docker APIs and Redis instances.

Before downloading the secondary stage payload, the script cleans the target system of a number of pre-existing infections and miners, as well as disabling a number of known security tools and software.

Figure 2: The downloader script

Following the initial clean up, the script would iterate through three functions to download the crypto-miner payload — salt-storer

SHA256 837d768875417578c0b1cab4bd0aa38146147799f643bb7b3c6c6d3d82d7aa2a

— from three different hard-coded servers. An MD5 check for the downloaded executable would be performed prior to execution. The below screenshot illustrates two out of the three downloader functions that would be invoked.

Figure 3: Two of the downloader functions

Second stage payload

Following the cryptographic checks, the downloaded ELF LSB executable kicks into action. No payload analysis was carried out, however it’s execution would result in a crypto-miner being installed and a C2 channel opened.

OSINT indicates that several new versions of the payload were observed carrying additional capabilities, including database dumping and advanced persistence methods. The variants detected by Darktrace’s AI included the more advanced “Version 5” payload purported to have worming capabilities, but in this case they were not observed directly.

Command and control

Upon the execution of an LSB executable, a plaintext HTTP C2 channel would be established, sending basic metadata about the infected host such as processor architecture, available resources, and whether root execution was achieved. This indicates that the C2 mechanisms were likely repurposed from other infections, as this particular infection would execute as root, making the respective component redundant.

Figure 4: A Command and control channel

The complete attack lifecycle was investigated and reported on by Darktrace’s Cyber AI Analyst, which automatically surfaced some crucial details regarding the C2 communication, including other servers that were seen making similar communication patterns, as seen in the bottom right below.

Figure 5: The Cyber AI Analyst automatically generating a natural-language summary of the overall security incident

Figure 6: Further information on the suspicious endpoints

Actions on target

Lastly, devices began mining for cryptocurrency. Cryptocurrency mining demands a substantial proportion of a device’s processing power, such as CPU and GPU, in order to calculate hashes. However, except for the occasional increase in CPU or RAM usage, it can go undetected for months as traditional security products do not normally detect its pattern of behavior as malicious.

Conclusion

Failing to patch vulnerabilities quickly and decisively can have serious consequences. Sometimes, however, the window of opportunity before an attack hits is too short for patching to be feasible. This example demonstrates how quickly unpatched vulnerabilities can be exploited following an initial public disclosure. And yet, even two months after SaltStack published the updates, many Salt servers remain unpatched and run the risk of becoming compromised.

In the case of Citrix, some exploits led to a ransomware attack. Darktrace’s AI-powered Immune System technology not only detected every stage of these ransomware attacks, but its autonomous response was able to halt any anomalous event and contain further damage.

Because new vulnerabilities are, by nature, unexpected, traditional security tools relying on rules and signatures don’t know to look for malicious activity that arises as a result. However, with its constantly evolving understanding of ‘normal’, Darktrace’s AI detects and investigates any unusual behavior, regardless of its origin or whether an attack has been seen before.

Crypto-mining is still favored among many threat actors due to its ability to generate profits, and a successfully infection can have a serious impact on the confidentiality and integrity of the corporate network. The need for Cyber AI that can detect new vulnerabilities and novel threats, and autonomously respond to stop an attack in its tracks, are critical to ensuring businesses remain secure in the face of cyber-criminals who are mobilizing to exploit vulnerabilities more quickly than ever.

IoCs:

IoCComment144.217.129[.]111Likely C2, URIs: /ms /h /s91.215.152[.]69Likely C2, URI: /h89.223.121[.]139Download of payload sa.sh217.12.210[.]192Download of payload sa.sh45.147.201[.]62Destination for crypto-mining217.12.210[.]245Download of payload salt_storer

Darktrace model breaches:

  • Device / Initial Breach Chain Compromise
  • Compromise / SSL or HTTP Beacon
  • Device / Large Number of Model Breaches
  • Anomalous Connection / New User Agent to IP Without Hostname
  • Anomalous File / Script from Rare External
  • Compromise / Beaconing Activity To External Rare
  • Anomalous Connection / Multiple Failed Connections to Rare Destination
  • Compromise / Sustained SSL or HTTP Increase
  • Compliance / Crypto Currency Mining Activity

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
Max Heinemeyer
Global Field CISO

More in this series

No items found.

Blog

/

/

April 24, 2025

The Importance of NDR in Resilient XDR

picture of hands typing on laptop Default blog imageDefault blog image

As threat actors become more adept at targeting and disabling EDR agents, relying solely on endpoint detection leaves critical blind spots.

Network detection and response (NDR) offers the visibility and resilience needed to catch what EDR can’t especially in environments with unmanaged devices or advanced threats that evade local controls.

This blog explores how threat actors can disable or bypass EDR-based XDR solutions and demonstrates how Darktrace’s approach to NDR closes the resulting security gaps with Self-Learning AI that enables autonomous, real-time detection and response.

Threat actors see local security agents as targets

Recent research by security firms has highlighted ‘EDR killers’: tools that deliberately target EDR agents to disable or damage them. These include the known malicious tool EDRKillShifter, the open source EDRSilencer, EDRSandblast and variants of Terminator, and even the legitimate business application HRSword.

The attack surface of any endpoint agent is inevitably large, whether the software is challenged directly, by contesting its local visibility and access mechanisms, or by targeting the Operating System it relies upon. Additionally, threat actors can readily access and analyze EDR tools, and due to their uniformity across environments an exploit proven in a lab setting will likely succeed elsewhere.

Sophos have performed deep research into the EDRShiftKiller tool, which ESET have separately shown became accessible to multiple threat actor groups. Cisco Talos have reported via TheRegister observing significant success rates when an EDR kill was attempted by ransomware actors.

With the local EDR agent silently disabled or evaded, how will the threat be discovered?

What are the limitations of relying solely on EDR?

Cyber attackers will inevitably break through boundary defences, through innovation or trickery or exploiting zero-days. Preventive measures can reduce but not completely stop this. The attackers will always then want to expand beyond their initial access point to achieve persistence and discover and reach high value targets within the business. This is the primary domain of network activity monitoring and NDR, which includes responsibility for securing the many devices that cannot run endpoint agents.

In the insights from a CISA Red Team assessment of a US CNI organization, the Red Team was able to maintain access over the course of months and achieve their target outcomes. The top lesson learned in the report was:

“The assessed organization had insufficient technical controls to prevent and detect malicious activity. The organization relied too heavily on host-based endpoint detection and response (EDR) solutions and did not implement sufficient network layer protections.”

This proves that partial, isolated viewpoints are not sufficient to track and analyze what is fundamentally a connected problem – and without the added visibility and detection capabilities of NDR, any downstream SIEM or MDR services also still have nothing to work with.

Why is network detection & response (NDR) critical?

An effective NDR finds threats that disable or can’t be seen by local security agents and generally operates out-of-band, acquiring data from infrastructure such as traffic mirroring from physical or virtual switches. This means that the security system is extremely inaccessible to a threat actor at any stage.

An advanced NDR such as Darktrace / NETWORK is fully capable of detecting even high-end novel and unknown threats.

Detecting exploitation of Ivanti CS/PS with Darktrace / NETWORK

On January 9th 2025, two new vulnerabilities were disclosed in Ivanti Connect Secure and Policy Secure appliances that were under malicious exploitation. Perimeter devices, like Ivanti VPNs, are designed to keep threat actors out of a network, so it's quite serious when these devices are vulnerable.

An NDR solution is critical because it provides network-wide visibility for detecting lateral movement and threats that an EDR might miss, such as identifying command and control sessions (C2) and data exfiltration, even when hidden within encrypted traffic and which an EDR alone may not detect.

Darktrace initially detected suspicious activity connected with the exploitation of CVE-2025-0282 on December 29, 2024 – 11 days before the public disclosure of the vulnerability, this early detection highlights the benefits of an anomaly-based network detection method.

Throughout the campaign and based on the network telemetry available to Darktrace, a wide range of malicious activities were identified, including the malicious use of administrative credentials, the download of suspicious files, and network scanning in the cases investigated.

Darktrace / NETWORK’s autonomous response capabilities played a critical role in containment by autonomously blocking suspicious connections and enforcing normal behavior patterns. At the same time, Darktrace Cyber AI Analyst™ automatically investigated and correlated the anomalous activity into cohesive incidents, revealing the full scope of the compromise.

This case highlights the importance of real-time, AI-driven network monitoring to detect and disrupt stealthy post-exploitation techniques targeting unmanaged or unprotected systems.

Unlocking adaptive protection for evolving cyber risks

Darktrace / NETWORK uses unique AI engines that learn what is normal behavior for an organization’s entire network, continuously analyzing, mapping and modeling every connection to create a full picture of your devices, identities, connections, and potential attack paths.

With its ability to uncover previously unknown threats as well as detect known threats using signatures and threat intelligence, Darktrace is an essential layer of the security stack. Darktrace has helped secure customers against attacks including 2024 threat actor campaigns against Fortinet’s FortiManager , Palo Alto firewall devices, and more.  

Stay tuned for part II of this series which dives deeper into the differences between NDR types.

Credit to Nathaniel Jones VP, Security & AI Strategy, FCISO & Ashanka Iddya, Senior Director of Product Marketing for their contribution to this blog.

Continue reading
About the author
Nathaniel Jones
VP, Security & AI Strategy, Field CISO

Blog

/

/

April 22, 2025

Obfuscation Overdrive: Next-Gen Cryptojacking with Layers

man looking at multiple computer screensDefault blog imageDefault blog image

Out of all the services honeypotted by Darktrace, Docker is the most commonly attacked, with new strains of malware emerging daily. This blog will analyze a novel malware campaign with a unique obfuscation technique and a new cryptojacking technique.

What is obfuscation?

Obfuscation is a common technique employed by threat actors to prevent signature-based detection of their code, and to make analysis more difficult. This novel campaign uses an interesting technique of obfuscating its payload.

Docker image analysis

The attack begins with a request to launch a container from Docker Hub, specifically the kazutod/tene:ten image. Using Docker Hub’s layer viewer, an analyst can quickly identify what the container is designed to do. In this case, the container is designed to run the ten.py script which is built into itself.

 Docker Hub Image Layers, referencing the script ten.py.
Figure 1: Docker Hub Image Layers, referencing the script ten.py.

To gain more information on the Python file, Docker’s built in tooling can be used to download the image (docker pull kazutod/tene:ten) and then save it into a format that is easier to work with (docker image save kazutod/tene:ten -o tene.tar). It can then be extracted as a regular tar file for further investigation.

Extraction of the resulting tar file.
Figure 2: Extraction of the resulting tar file.

The Docker image uses the OCI format, which is a little different to a regular file system. Instead of having a static folder of files, the image consists of layers. Indeed, when running the file command over the sha256 directory, each layer is shown as a tar file, along with a JSON metadata file.

Output of the file command over the sha256 directory.
Figure 3: Output of the file command over the sha256 directory.

As the detailed layers are not necessary for analysis, a single command can be used to extract all of them into a single directory, recreating what the container file system would look like:

find blobs/sha256 -type f -exec sh -c 'file "{}" | grep -q "tar archive" && tar -xf "{}" -C root_dir' \;

Result of running the command above.
Figure 4: Result of running the command above.

The find command can then be used to quickly locate where the ten.py script is.

find root_dir -name ten.py

root_dir/app/ten.py

Details of the above ten.py script.
Figure 5: Details of the above ten.py script.

This may look complicated at first glance, however after breaking it down, it is fairly simple. The script defines a lambda function (effectively a variable that contains executable code) and runs zlib decompress on the output of base64 decode, which is run on the reversed input. The script then runs the lambda function with an input of the base64 string, and then passes it to exec, which runs the decoded string as Python code.

To help illustrate this, the code can be cleaned up to this simplified function:

def decode(input):
   reversed = input[::-1]

   decoded = base64.decode(reversed)
   decompressed = zlib.decompress(decoded)
   return decompressed

decoded_string = decode(the_big_text_blob)
exec(decoded_string) # run the decoded string

This can then be set up as a recipe in Cyberchef, an online tool for data manipulation, to decode it.

Use of Cyberchef to decode the ten.py script.
Figure 6: Use of Cyberchef to decode the ten.py script.

The decoded payload calls the decode function again and puts the output into exec. Copy and pasting the new payload into the input shows that it does this another time. Instead of copy-pasting the output into the input all day, a quick script can be used to decode this.

The script below uses the decode function from earlier in order to decode the base64 data and then uses some simple string manipulation to get to the next payload. The script will run this over and over until something interesting happens.

# Decode the initial base64

decoded = decode(initial)
# Remove the first 11 characters and last 3

# so we just have the next base64 string

clamped = decoded[11:-3]

for i in range(1, 100):
   # Decode the new payload

   decoded = decode(clamped)
   # Print it with the current step so we

   # can see what’s going on

   print(f"Step {i}")

   print(decoded)
   # Fetch the next base64 string from the

   # output, so the next loop iteration will

   # decode it

   clamped = decoded[11:-3]

Result of the 63rd iteration of this script.
Figure 7: Result of the 63rd iteration of this script.

After 63 iterations, the script returns actual code, accompanied by an error from the decode function as a stopping condition was never defined. It not clear what the attacker’s motive to perform so many layers of obfuscation was, as one round of obfuscation versus several likely would not make any meaningful difference to bypassing signature analysis. It’s possible this is an attempt to stop analysts or other hackers from reverse engineering the code. However,  it took a matter of minutes to thwart their efforts.

Cryptojacking 2.0?

Cleaned up version of the de-obfuscated code.
Figure 8: Cleaned up version of the de-obfuscated code.

The cleaned up code indicates that the malware attempts to set up a connection to teneo[.]pro, which appears to belong to a Web3 startup company.

Teneo appears to be a legitimate company, with Crunchbase reporting that they have raised USD 3 million as part of their seed round [1]. Their service allows users to join a decentralized network, to “make sure their data benefits you” [2]. Practically, their node functions as a distributed social media scraper. In exchange for doing so, users are rewarded with “Teneo Points”, which are a private crypto token.

The malware script simply connects to the websocket and sends keep-alive pings in order to gain more points from Teneo and does not do any actual scraping. Based on the website, most of the rewards are gated behind the number of heartbeats performed, which is likely why this works [2].

Checking out the attacker’s dockerhub profile, this sort of attack seems to be their modus operandi. The most recent container runs an instance of the nexus network client, which is a project to perform distributed zero-knowledge compute tasks in exchange for cryptocurrency.

Typically, traditional cryptojacking attacks rely on using XMRig to directly mine cryptocurrency, however as XMRig is highly detected, attackers are shifting to alternative methods of generating crypto. Whether this is more profitable remains to be seen. There is not currently an easy way to determine the earnings of the attackers due to the more “closed” nature of the private tokens. Translating a user ID to a wallet address does not appear to be possible, and there is limited public information about the tokens themselves. For example, the Teneo token is listed as “preview only” on CoinGecko, with no price information available.

Conclusion

This blog explores an example of Python obfuscation and how to unravel it. Obfuscation remains a ubiquitous technique employed by the majority of malware to aid in detection/defense evasion and being able to de-obfuscate code is an important skill for analysts to possess.

We have also seen this new avenue of cryptominers being deployed, demonstrating that attackers’ techniques are still evolving - even tried and tested fields. The illegitimate use of legitimate tools to obtain rewards is an increasingly common vector. For example,  as has been previously documented, 9hits has been used maliciously to earn rewards for the attack in a similar fashion.

Docker remains a highly targeted service, and system administrators need to take steps to ensure it is secure. In general, Docker should never be exposed to the wider internet unless absolutely necessary, and if it is necessary both authentication and firewalling should be employed to ensure only authorized users are able to access the service. Attacks happen every minute, and even leaving the service open for a short period of time may result in a serious compromise.

References

1. https://www.crunchbase.com/funding_round/teneo-protocol-seed--a8ff2ad4

2. https://teneo.pro/

Continue reading
About the author
Nate Bill
Threat Researcher
Your data. Our AI.
Elevate your network security with Darktrace AI