January 4, 2023

BlackMatter's Smash-and-Grab Ransom Attack Incident Analysis

Stay informed on cybersecurity trends! Read about a BlackMatters ransom attack incident and Darktrace's analysis on how RESPOND could have stopped the attack.

Written by

The Darktrace Analyst Team

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

The Darktrace Analyst Team

Jan 2023

Only a few years ago, popular reporting announced that the days of smash-and-grab attacks were over and that a new breed of hackers were taking over with subtler, ‘low-and-slow’ tactics [1]. Although these have undoubtedly appeared, smash-and-grab have quickly become overlooked – perhaps with worrying consequences. Last year, Google saw repeated phishing campaigns using cookie theft malware and most recently, reports of hacktivists using similar techniques have been identified during the 2022 Ukraine Conflict [2 & 3]. Where did their inspiration come from? For larger APT groups such as BlackMatter, which first appeared in the summer of 2021, smash-and-grabs never went out of fashion.

This blog dissects a BlackMatter ransomware attack that hit an organization trialing Darktrace back in 2021. The case reveals what can happen when a security team does not react to high-priority alerts.

When entire ransomware attacks can be carried out over the course of just 48 hours, there is a high risk to relying on security teams to react to detection notifications and prevent damage before the threat escalates. Although there has been hesitancy in its uptake [4], this blog also demonstrates the need for automated response solutions like Darktrace RESPOND.

The Name Game: Untangling BlackMatter, REvil, and DarkSide

Despite being a short-lived criminal organization on the surface [5], a number of parallels have now been drawn between the TTPs (Tactics, Techniques and Procedures) of the newer BlackMatter group and those of the retired REvil and DarkSide organizations [6].

Prior to their retirement, DarkSide and REvil were perhaps the biggest names in cyber-crime, responsible for two of last year’s most devastating ransomware attacks. Less than two weeks after the Colonial Pipeline attack, DarkSide announced it was shutting down its operation [7]. Meanwhile the FBI shutdown REvil in January 2022 after its devastating Fourth of July Kaseya attacks and a failed return in September [8]. It is now suspected that members from one or both went on to form BlackMatter.

This rebranding strategy parallels the smash-and-grab attacks these groups now increasingly employ: they make their money, and a lot of noise, and when they’re found out, they disappear before organizations or governments can pull together their threat intelligence and organize an effective response. When they return days, weeks or months later, they do so having implemented enough small changes to render themselves and their attacks unrecognizable. That is how DarkSide can become BlackMatter, and how its attacks can slip through security systems trained on previously encountered threats.

Attack Details

In September 2021 Darktrace was monitoring a US marketing agency which became the victim of a double extortion ransomware attack that bore hallmarks of a BlackMatter operation. This began when a single domain-authenticated device joined the company’s network. This was likely a pre-infected company device being reconnected after some time offline.

Only 15 minutes after joining, the device began SMB and ICMP scanning activities towards over 1000 different internal IPs. There was also a large spike of requests for Epmapper, which suggested an intent for RPC-based lateral movement. Although one credential was particularly prominent, multiple were used including labelled admin credentials. Given it’s unexpected nature, this recon quickly triggered a chain of DETECT/Network model breaches which ensured that Darktrace’s SOC were alerted via the Proactive Threat Notification service. Whilst SOC analysts began to triage the activity, the organization failed to act on any of the alerts they received, leaving the detected threat to take root within their digital environment.

Shortly after, a series of C2 beaconing occurred towards an endpoint associated with Cobalt Strike [9]. This was accompanied by a range of anomalous WMI bind requests to svcctl, SecAddr and further RPC connections. These allowed the initial compromised device to quickly infect 11 other devices. With continued scanning over the next day, valuable data was soon identified. Across several transfers, 230GB of internal data was then exfiltrated from four file servers via SSH port 22. This data was then made unusable to the organization through encryption occurring via SMB Writes and Moves/Renames with the randomly generated extension ‘.qHefKSmfd’. Finally a ransom note titled ‘qHefKSmfd.README.txt’ was dropped.

This ransom note was appended with the BlackMatter ASCII logo:

*Figure 1- The ASCII logo which accompanied BlackMatter’s ransom note*

Although Darktrace DETECT and Cyber AI Analyst continued to provide live alerting, the actor successfully accomplished their mission.

There are numerous reasons that an organization may fail to organize a response to a threat, (including resource shortages, out of hours attacks, and groups that simply move too fast). Without Darktrace’s RESPOND capabilities enabled, the threat actors could proceed this attack without obstacles.

*Figure 2- Cyber AI Analyst breaks down the stages of the attack [Note: this screenshot is from V5 of DETECT/Network]*

How would the attack have unfolded with RESPOND?

Armed with Darktrace’s evolving knowledge of ‘self’ for the customer’s unique digital environment, RESPOND would have activated within seconds of the first network scan, which was recognized as highly anomalous. The standard action taken here would usually involve enforcing the standard ‘pattern of life’ for the compromised device over a set time period in order to halt the anomaly while allowing the business to continue operating as normal.

RESPOND constantly re-evaluates threats as attacks unfold. Had the first stage still been successful, it would have continued to take targeted action at each corresponding stage of this attack. RESPOND models would have alerted to block the external connections to C2 servers over port 443, the outbound exfil attempts and crucially the SMB write activity over port 445 related to encryption.

As DETECT and RESPOND feed into one another, Darktrace would have continued to assess its actions as BlackMatter pivoted tactics. These actions buy back critical time for security teams that may not be in operation over the weekend, and stun the attacker into place without applying overly aggressive responses that create more problems than they solve.

Ultimately although this incident did not resolve autonomously, in response to the ransom event, Darktrace offered to enable RESPOND and set it in active mode for ransomware indicators across all client and server devices. This ensured an event like this would not occur again.

Why does RESPOND work?

Response solutions must be accurate enough to fire only when there is a genuine threat, configurable enough to let the user stay in the driver’s seat, and intelligent enough to know the right action to take to contain only the malicious activity- without disrupting normal business operations.

This is only possible if you can establish what ‘normal’ is for any one organization. And this is how Darktrace’s RESPOND product family ensures its actions are targeted and proportionate. By feeding off DETECT alerting which highlights subtle or large deviations across the network, cloud and SaaS, RESPOND can provide a measured response to the potential threat. This includes actions such as:

Enforcing the device’s ‘pattern of life’ for a given length of time
Enforcing the ‘group pattern of life’ (stopping a device from doing anything its peers haven’t done in the past)
Blocking connections of a certain type to a certain destination
Logging out of a cloud account
‘Smart quarantining’ an endpoint device- maintaining access to VPNs and company’s AV solution

Conclusion

In its report on BlackMatter [10], CISA recommended that organizations invest in network monitoring tools with the capacity to investigate anomalous activity. Picking up on unusual behavior rather than predetermined rules and signatures is an important step in fighting back against new threats. As this particular story shows, however, detection alone is not always enough. Turning on RESPOND, which takes immediate and precise action to contain threats, regardless of when and where they come in, is the best way to counter smash-and-grab attacks and protect organizations’ digital assets. There is little doubt that the threat actors behind BlackMatter will or have already returned with new names and strategies- but organizations with RESPOND will be ready for them.

Appendices

Darktrace Model Detections (in order of breach)

Those with the ‘PTN’ prefix were alerted directly to Darktrace’s 24/7 SOC team.

Device / ICMP Address Scan
Device / Suspicious SMB Scanning Activity
(PTN) Device / Suspicious Network Scan Activity
Anomalous Connection / SMB Enumeration
Device / Possible RPC Lateral Movement
Device / Active Directory Reconnaissance
Unusual Activity / Possible RPC Recon Activity
Device / Possible SMB/NTLM Reconnaissance
Compliance / Default Credential Usage
Device / New or Unusual Remote Command Execution
Anomalous Connection / New or Uncommon Service Control
Device / New or Uncommon SMB Named Pipe
Device / SMB Session Bruteforce
Device / New or Uncommon WMI Activity
(PTN) Device / Multiple Lateral Movement Model Breaches
Compromise / Sustained SSL or HTTP Increase
Compromise / SSL or HTTP Beacon
Compromise / Sustained TCP Beaconing Activity To Rare Endpoint
Device / Anomalous SMB Followed By Multiple Model Breaches
Device / Anomalous RDP Followed By Multiple Model Breaches
Anomalous Server Activity / Rare External from Server
Anomalous Connection / Anomalous SSL without SNI to New External
Anomalous Connection / Rare External SSL Self-Signed
Device / Long Agent Connection to New Endpoint
Compliance / SMB Drive Write
Anomalous Connection / Unusual Admin SMB Session
Anomalous Connection / High Volume of New or Uncommon Service Control
Anomalous Connection / Unusual Admin RDP Session
Device / Suspicious File Writes to Multiple Hidden SMB Shares
Anomalous Connection / Multiple Connections to New External TCP Port
Compliance / SSH to Rare External Destination
Anomalous Connection / Uncommon 1 GiB Outbound
Anomalous Connection / Data Sent to Rare Domain
Anomalous Connection / Download and Upload
(PTN) Unusual Activity / Enhanced Unusual External Data Transfer
Anomalous File / Internal / Additional Extension Appended to SMB File
(PTN) Compromise / Ransomware / Suspicious SMB Activity

List of IOCs

Reference List

[1] https://www.designnews.com/industrial-machinery/new-age-hackers-are-ditching-smash-and-grab-techniques

[2] https://cybernews.com/cyber-war/how-do-smash-and-grab-cyberattacks-help-ukraine-in-waging-war/

[3] https://blog.google/threat-analysis-group/phishing-campaign-targets-youtube-creators-cookie-theft-malware/

[4] https://www.ukcybersecuritycouncil.org.uk/news-insights/articles/the-benefits-of-automation-to-cyber-security/

[5] https://techcrunch.com/2021/11/03/blackmatter-ransomware-shut-down/

[6] https://www.trellix.com/en-us/about/newsroom/stories/research/blackmatter-ransomware-analysis-the-dark-side-returns.html

[7] https://www.nytimes.com/2021/05/14/business/darkside-pipeline-hack.html

[8] https://techcrunch.com/2022/01/14/fsb-revil-ransomware/

[9] https://www.virustotal.com/gui/domain/georgiaonsale.com/community

[10] https://www.cisa.gov/uscert/ncas/alerts/aa21-291a

Credit to: Andras Balogh, SOC Analyst and Gabriel Few-Wiegratz, Threat Intelligence Content Production Lead

Written by

The Darktrace Analyst Team

Inside the SOC

Written by

The Darktrace Analyst Team

VP, Security & AI Strategy, Field CISO

Senior Product Marketing Manager, Email

Watch the NIS2 Webinar

Blog

Identity

July 3, 2025

Top Eight Threats to SaaS Security and How to Combat Them

The latest on the identity security landscape

Following the mass adoption of remote and hybrid working patterns, more critical data than ever resides in cloud applications – from Salesforce and Google Workspace, to Box, Dropbox, and Microsoft 365.

On average, a single organization uses 130 different Software-as-a-Service (SaaS) applications, and 45% of organizations reported experiencing a cybersecurity incident through a SaaS application in the last year.

As SaaS applications look set to remain an integral part of the digital estate, organizations are being forced to rethink how they protect their users and data in this area.

What is SaaS security?

SaaS security is the protection of cloud applications. It includes securing the apps themselves as well as the user identities that engage with them.

Below are the top eight threats that target SaaS security and user identities.

1. Account Takeover (ATO)

Attackers gain unauthorized access to a user’s SaaS or cloud account by stealing credentials through phishing, brute-force attacks, or credential stuffing. Once inside, they can exfiltrate data, send malicious emails, or escalate privileges to maintain persistent access.

2. Privilege escalation

Cybercriminals exploit misconfigurations, weak access controls, or vulnerabilities to increase their access privileges within a SaaS or cloud environment. Gaining admin or superuser rights allows attackers to disable security settings, create new accounts, or move laterally across the organization.

3. Lateral movement

Once inside a network or SaaS platform, attackers move between accounts, applications, and cloud workloads to expand their foot- hold. Compromised OAuth tokens, session hijacking, or exploited API connections can enable adversaries to escalate access and exfiltrate sensitive data.

4. Multi-Factor Authentication (MFA) bypass and session hijacking

Threat actors bypass MFA through SIM swapping, push bombing, or exploiting session cookies. By stealing an active authentication session, they can access SaaS environments without needing the original credentials or MFA approval.

5. OAuth token abuse

Attackers exploit OAuth authentication mechanisms by stealing or abusing tokens that grant persistent access to SaaS applications. This allows them to maintain access even if the original user resets their password, making detection and mitigation difficult.

6. Insider threats

Malicious or negligent insiders misuse their legitimate access to SaaS applications or cloud platforms to leak data, alter configurations, or assist external attackers. Over-provisioned accounts and poor access control policies make it easier for insiders to exploit SaaS environments.

7. Application Programming Interface (API)-based attacks

SaaS applications rely on APIs for integration and automation, but attackers exploit insecure endpoints, excessive permissions, and unmonitored API calls to gain unauthorized access. API abuse can lead to data exfiltration, privilege escalation, and service disruption.

8. Business Email Compromise (BEC) via SaaS

Adversaries compromise SaaS-based email platforms (e.g., Microsoft 365 and Google Workspace) to send phishing emails, conduct invoice fraud, or steal sensitive communications. BEC attacks often involve financial fraud or data theft by impersonating executives or suppliers.

BEC heavily uses social engineering techniques, tailoring messages for a specific audience and context. And with the growing use of generative AI by threat actors, BEC is becoming even harder to detect. By adding ingenuity and machine speed, generative AI tools give threat actors the ability to create more personalized, targeted, and convincing attacks at scale.

Protecting against these SaaS threats

Traditionally, security leaders relied on tools that were focused on the attack, reliant on threat intelligence, and confined to a single area of the digital estate.

However, these tools have limitations, and often prove inadequate for contemporary situations, environments, and threats. For example, they may lack advanced threat detection, have limited visibility and scope, and struggle to integrate with other tools and infrastructure, especially cloud platforms.

AI-powered SaaS security stays ahead of the threat landscape

New, more effective approaches involve AI-powered defense solutions that understand the digital business, reveal subtle deviations that indicate cyber-threats, and action autonomous, targeted responses.

[related-resource]

‍

About the author

Carlos Gray

Senior Product Marketing Manager, Email

Blog

Proactive Security

July 2, 2025

Pre-CVE Threat Detection: 10 Examples Identifying Malicious Activity Prior to Public Disclosure of a Vulnerability

‍

Vulnerabilities are weaknesses in a system that can be exploited by malicious actors to gain unauthorized access or to disrupt normal operations. Common Vulnerabilities and Exposures (or CVEs) are a list of publicly disclosed cybersecurity vulnerabilities that can be tracked and mitigated by the security community.

When a vulnerability is discovered, the standard practice is to report it to the vendor or the responsible organization, allowing them to develop and distribute a patch or fix before the details are made public. This is known as responsible disclosure.

With a record-breaking 40,000 CVEs reported for 2024 and a predicted higher number for 2025 by the Forum for Incident Response and Security Teams (FIRST) [1], anomaly-detection is essential for identifying these potential risks. The gap between exploitation of a zero-day and disclosure of the vulnerability can sometimes be considerable, and retroactively attempting to identify successful exploitation on your network can be challenging, particularly if taking a signature-based approach.

Detecting threats without relying on CVE disclosure

Abnormal behaviors in networks or systems, such as unusual login patterns or data transfers, can indicate attempted cyber-attacks, insider threats, or compromised systems. Since Darktrace does not rely on rules or signatures, it can detect malicious activity that is anomalous even without full context of the specific device or asset in question.

‍For example, during the Fortinet exploitation late last year, the Darktrace Threat Research team were investigating a different Fortinet vulnerability, namely CVE 2024-23113, for exploitation when Mandiant released a security advisory around CVE 2024-47575, which aligned closely with Darktrace’s findings.

Retrospective analysis like this is used by Darktrace’s threat researchers to better understand detections across the threat landscape and to add additional context.

Below are ten examples from the past year where Darktrace detected malicious activity days or even weeks before a vulnerability was publicly disclosed.

ten examples from the past year where Darktrace detected malicious activity days or even weeks before a vulnerability was publicly disclosed.

Trends in pre-cve exploitation

Often, the disclosure of an exploited vulnerability can be off the back of an incident response investigation related to a compromise by an advanced threat actor using a zero-day. Once the vulnerability is registered and publicly disclosed as having been exploited, it can kick off a race between the attacker and defender: attack vs patch.

Nation-state actors, highly skilled with significant resources, are known to use a range of capabilities to achieve their target, including zero-day use. Often, pre-CVE activity is “low and slow”, last for months with high operational security. After CVE disclosure, the barriers to entry lower, allowing less skilled and less resourced attackers, like some ransomware gangs, to exploit the vulnerability and cause harm. This is why two distinct types of activity are often seen: pre and post disclosure of an exploited vulnerability.

Darktrace saw this consistent story line play out during several of the Fortinet and PAN OS threat actor campaigns highlighted above last year, where nation-state actors were seen exploiting vulnerabilities first, followed by ransomware gangs impacting organizations [2].

The same applies with the recent SAP Netweaver exploitations being tied to a China based threat actor earlier this spring with subsequent ransomware incidents being observed [3].

Autonomous Response

Anomaly-based detection offers the benefit of identifying malicious activity even before a CVE is disclosed; however, security teams still need to quickly contain and isolate the activity.

For example, during the Ivanti chaining exploitation in the early part of 2025, a customer had Darktrace’s Autonomous Response capability enabled on their network. As a result, Darktrace was able to contain the compromise and shut down any ongoing suspicious connectivity by blocking internal connections and enforcing a “pattern of life” on the affected device.

This pre-CVE detection and response by Darktrace occurred 11 days before any public disclosure, demonstrating the value of an anomaly-based approach.

In some cases, customers have even reported that Darktrace stopped malicious exploitation of devices several days before a public disclosure of a vulnerability.

For example, During the ConnectWise exploitation, a customer informed the team that Darktrace had detected malicious software being installed via remote access. Upon further investigation, four servers were found to be impacted, while Autonomous Response had blocked outbound connections and enforced patterns of life on impacted devices.

Conclusion

By continuously analyzing behavioral patterns, systems can spot unusual activities and patterns from users, systems, and networks to detect anomalies that could signify a security breach.

Through ongoing monitoring and learning from these behaviors, anomaly-based security systems can detect threats that traditional signature-based solutions might miss, while also providing detailed insights into threat tactics, techniques, and procedures (TTPs). This type of behavioral intelligence supports pre-CVE detection, allows for a more adaptive security posture, and enables systems to evolve with the ever-changing threat landscape.

Credit to Nathaniel Jones (VP, Security & AI Strategy, Field CISO), Emma Fougler (Global Threat Research Operations Lead), Ryan Traill (Analyst Content Lead)

References and further reading:

Related Darktrace blogs:

‍

*Self-reported by customer, confirmed afterwards.

**Updated January 2024 blog now reflects current findings

About the author

Nathaniel Jones

VP, Security & AI Strategy, Field CISO

Your data. Our AI.

Elevate your network security with Darktrace AI

Get a demo

Check out this article by Darktrace: BlackMatter's Smash-and-Grab Ransom Attack Incident Analysis

BlackMatter's Smash-and-Grab Ransom Attack Incident Analysis

The Name Game: Untangling BlackMatter, REvil, and DarkSide

Attack Details

How would the attack have unfolded with RESPOND?

Why does RESPOND work?

Conclusion

List of IOCs

Reference List

Pre-CVE Threat Detection: 10 Examples Identifying Malicious Activity Prior to Public Disclosure of a Vulnerability

Top Eight Threats to SaaS Security and How to Combat Them

Enjoying the blog?

More in this series

Patch and Persist: Darktrace’s Detection of Blind Eagle (APT-C-36)

Customer Case Study: Leading Petrochemical Manufacturer

Tracking CVE-2025-31324: Darktrace’s detection of SAP Netweaver exploitation before and after disclosure

Blog

Identity

July 3, 2025

Top Eight Threats to SaaS Security and How to Combat Them

The latest on the identity security landscape

What is SaaS security?

1. Account Takeover (ATO)

2. Privilege escalation

3. Lateral movement

4. Multi-Factor Authentication (MFA) bypass and session hijacking

5. OAuth token abuse

6. Insider threats

7. Application Programming Interface (API)-based attacks

8. Business Email Compromise (BEC) via SaaS

Protecting against these SaaS threats

AI-powered SaaS security stays ahead of the threat landscape

Blog

Proactive Security

July 2, 2025

Pre-CVE Threat Detection: 10 Examples Identifying Malicious Activity Prior to Public Disclosure of a Vulnerability

Detecting threats without relying on CVE disclosure

Below are ten examples from the past year where Darktrace detected malicious activity days or even weeks before a vulnerability was publicly disclosed.

Trends in pre-cve exploitation

Autonomous Response

Conclusion

References and further reading:

Related Darktrace blogs: