ブログ
/
Network
/
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.
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
Default blog image
04
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

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

More in this series

No items found.

Blog

/

AI

/

June 24, 2026

A New Security Challenge: The Curious Case of Prompt Language Analysis

Default blog imageDefault blog image

Why prompt analysis is emerging as a key AI security challenge

If securing AI has been one of the defining cybersecurity conversations of the past year, prompt analysis is quickly becoming one of its most interesting frontiers.

Security leaders are under pressure to understand how AI is being used across the business. In some organizations, that means governing employee use of chatbots. In others, it means overseeing copilots embedded into SaaS platforms, monitoring coding assistants, or assessing the growing footprint of autonomous agents. However different these use cases may appear on the surface, they share a common factor: humans and machines are usually interacting with enterprise systems through language.  

How prompt language differs from traditional security telemetry

For years, defenders have become used to working with familiar forms of telemetry: email traffic, network connections, API calls, endpoint processes, authentication events. Prompt language is different. It is not simply another log source. It is an expression of intent, instruction, curiosity, urgency, and sometimes manipulation. It reflects the end-goal of a user or agent, but not always with enough surrounding context to interpret the risk correctly.

Why existing security approaches only partially explain prompt risk

A growing number of vendors are approaching the task of securing AI from the angle they know best. Perimeter vendors are extending web or browser controls into AI usage. Identity vendors are emphasizing agent permissions and access governance. Data security and DLP providers are focusing on content inspection and exfiltration risk. All of these perspectives matter, but individually can’t fully explain the problem.

The challenge with securing AI is not just that a new application category has emerged. It is that language has become a new operating layer in the enterprise.

Employees now use prompts to summarize documents, generate code, analyze spreadsheets, query internal knowledge, and trigger multi-step actions through agents. In each case, prompt language acts as the interface between human intent and machine execution. That makes prompts incredibly valuable from a security perspective as they can hint at misuse, policy violations, data exposure, or attempts to circumvent controls. However, they can also be deeply ambiguous when viewed in isolation. That ambiguity is the heart of the issue.

Prompts as behavioral signals, not just text to classify

A prompt by itself tells you what was asked. It does not necessarily tell you whether the request is expected, risky, accidental, or entirely legitimate in context. Two nearly identical prompts can carry very different meanings depending on the role and function of who issued them, what systems they can access, and what actions followed. In other words, prompts are not just text to classify. They are behavioral signals to interpret.

Example: How context changes prompt risk entirely

Consider a common enterprise scenario. An employee is pulled into a new project with an aggressive deadline. Almost overnight, their use of AI tools spikes. They begin prompting more frequently, working across unfamiliar documents, querying new data sources, and interacting with more systems than usual to accelerate delivery. Viewed narrowly, this may look suspicious. Prompt volume increases, file access patterns change, API and SaaS activity rise. From some vantage points, it may resemble insider risk or unmanaged AI usage.

But now add context. Imagine that, earlier that day, the employee received instructions from a senior leader asking them to support a time-sensitive initiative. Their communication history shows that this leader is a legitimate reporting-line superior. Their recent collaboration patterns align with the new project team. Their subsequent activity, while unusual for that individual’s baseline, is consistent with the business task they were assigned.

What initially looked like a risk event may actually be a normal response to business pressure. Without the surrounding context of communication, organizational relationships, and broader behavioral patterns, prompt activity alone could generate more noise than insight.

The reverse is also true. A prompt may appear benign on the surface while the context around it suggests elevated risk. A request that seems routine could originate from a compromised user, a newly connected external agent, a shadow AI workflow, or a user acting outside their normal role. The language itself may not contain anything obviously malicious, but the surrounding conditions may tell a very different story.

What security teams need to analyze prompts effectively

The future of prompt analysis is not just about understanding language. It is about understanding language in context.

To do that well, security teams need more than prompt inspection. They need to understand:

  • Who is issuing the prompt, whether human or agent
  • How that identity normally behaves across the enterprise
  • What systems, data, and workflows are connected to the interaction
  • Which relationships and communications explain the surrounding activity
  • Whether the downstream actions align with expected business behavior

When those layers are absent, prompt analysis can become another isolated control surface: useful in theory, but limited in practice. Security teams may detect unusual wording but miss the operational function behind it, overreact to benign changes in behavior, or miss subtle misuse because the prompt itself did not appear dangerous.

How organizations should think about prompt analysis going forward

Security teams have seen this pattern before. In the cloud, posture without runtime context left important gaps. In identity, access control without behavioral understanding missed misuse that looked legitimate on paper. In data security, content inspection without business context often created friction without resolving risk. AI is exposing the same lesson again: controls are strongest when they are coordinated, not isolated. As organizations work to secure AI and identify gaps across their security operations, prompt analysis will become an increasingly important source of insight, but only as part of a broader strategy.

Prompt analysis will undoubtedly become more common, as prompts are one of the clearest windows into how people and agents are using AI systems. However, what matters most is not simply collecting prompts or filtering dangerous phrases, but being able to place that language inside a wider behavioral and operational picture.

Organizations that already have a broader understanding of how work gets done across the enterprise will be better positioned to make sense of prompt language as this category matures. They will be better able to distinguish urgency from abuse, experimentation from exfiltration, and productive AI adoption from hidden risk.

Figure 1: Darktrace / SECURE AI reconstructs the full sequence of events, showing every user and agent interaction in context, with risky prompts highlighted and categorized, including PII, sensitive data, and other policy violations.

At Darktrace, this is the key lesson emerging from the market: prompt language does matter, but it does not stand alone. It is most valuable when treated as a new behavioral input that can enrich understanding across the enterprise, not as a self-contained source of truth.

Why prompts become less useful when analyzed in isolation

The curious case of prompt language analysis, then, is this: the more important prompts become, the less useful they are in a vacuum.

The real opportunity is not just to see what was asked. It is to understand why it was asked, what it meant in that moment, and what happened next.

For a deeper look at how organizations are approaching this challenge from the strengths of prompt analysis to its limitations in isolation see Prompt Security in Enterprise AI: Strengths, Weaknesses, and Common Approaches, which expands on the role prompt-level controls play within a broader, context-driven security strategy.

Continue reading
About the author
Nabil Zoldjalali
VP, Field CISO

Blog

/

AI

/

June 23, 2026

サイバーセキュリティにおけるフロンティアAIの利用を推進: ダークトレース、OpenAIのDaybreakサイバーパートナープログラムに参加、防御AIのインテグレーションを模索

Default blog imageDefault blog image

ダークトレース、OpenAIのDaybreakサイバーパートナープログラムに参加

今日、ダークトレースがOpenAIのDaybreakサイバーパートナープログラムに参加したことが発表されました。私たちはOpenAIと協調して、OpenAIのサイバー機能をダークトレースの製品およびサービスにどう統合できるかを検証することで、ダークトレースの顧客に対して新たな機能を提供していきます。

このパートナーシップは、ダークトレースのビヘイビアAIモデリングをOpenAIの先進的コンテキスト機能と組み合わせることによりセキュリティチームに対して新たなレベルの理解を提供する、画期的な機会となります。この効果を理解していただくために、私たちがこの問題についてどう考えているかを説明することから始めたいと思います。

ダークトレースでは、サイバーセキュリティは防御対象のビジネスを理解する必要があるという基本的信念に基づいてAIを構築してきました。そのため、当社の自己学習型AIは、ユーザーやアイデンティティ、ネットワークやクラウド、Eメールやコラボレーションツール、そして現在はDarktrace / SECURE AI™の展開によりAIシステムやエージェントまでを含めて、各組織のデジタル環境全体における正常および異常な動作の理解を支援するよう設計されています。

私たちの目標は、これまでも単に既知の攻撃をより速く見つけることではありませんでした。自分たちの組織がどのように動作しているか、潜在的なリスクと影響、そして混乱がどこで起こり得るかを防御者が理解し、これまで見たことも想像したこともない未知の脅威に備えられるようにするためでした。

それはまさに今日の脅威ランドスケープで起こっていることです。攻撃は常に変化し続け、手法は移り変わり、インフラは進化し、攻撃者はより速く、正確に、そして状況に応じて動いています。そして今や彼らにはさらに多くの自動化とAIが味方についています。攻撃者は、アイデンティティ、信頼されたサービス、SaaSアプリケーション、およびビジネスワークフローを悪用しています。脅威は必ず外部から侵入しているわけではありません。脅威はしばしば組織内部から、内部関係者による脅威や悪意を持ったエージェントの形でやって来ることもあります。 

こうした現実のなかで、防御者は組織についての深いAIモデリングと、特定された脅威を具体的なビジネスコンテキストに結びつけ、この情報を現実の価値に変換し、リスクが障害に発展する前にアクションを取ることができるAIを必要としています。

私たちがOpenAIとの提携に見出しているチャンスはここにあります。

OpenAIのDaybreakサイバーパートナープログラムとは何か、そしてなぜダークトレースが参加するのか

OpenAI Daybreakサイバーパートナープログラムは、サイバーセキュリティへのAIの安全な利用を推進するためのプログラムです。プログラムの新たな段階として、OpenAIはダークトレースを含む選ばれた信頼できるパートナーと協調し、範囲を限定した製品インテグレーション、マネージド型サービス、パートナーを通じて提供される防御機能を検証します。私たちはOpenAIの高度なフロンティアAI機能が、日々利用しているツールやワークフローを通じてどのように防御者を支援できるかを模索します。

ダークトレースにとって、これは私たちの専門知識と過去10年間にわたって行ってきた取り組みの自然な延長線上にあります。それは、最も効果的なAI技術の組み合わせを安全かつ確実に適用することにより、組織を理解し、悪意あるアクティビティを最も早い兆候で検知し、サイバー防御者がより迅速に行動できるよう支援することです。

OpenAI Daybreakサイバーパートナープログラムで利用可能な高度なモデルとより精密なセーフガードを活用することで、ダークトレースとOpenAIは、組織のデジタルエステートについてのDarktraceのリアルタイムの動作理解と、広範なビジネスコンテキストを解釈するOpenAIの能力を組み合わせます。  

このユニークかつ強力な知見の組み合わせにより、技術的リスクについてより深いコンテキストを提供し、収益、業務、レジリエンスへの潜在的な影響に基づいて作業負荷や調査の優先順位を判断するのに役立てることができます。さらに、セキュリティチームや経営幹部に対して、どのイベントがビジネスにとって最も重要であるか、なぜ重要であるか、そしてどのような対応を取るべきかについての情報を提供することができます。たとえば、エージェントが侵害されていることを見つけるだけでなく、その侵害されたエージェントが今後3時間以内に注文の履行を停止させる可能性がある、ということを指摘することができます。

なぜダークトレースとOpenAIの提携が防御者にとって重要なのか

今日のセキュリティチームは、より多くのアタックサーフェスを管理し、より複雑な環境を保護しなければならず、脅威の量も増大しています。

迅速に行動する能力はきわめて重要ですが、それに加えて最もビジネスに影響を与えるリスクに集中できることも必要です。攻撃者がAIを使って大規模なフィッシングを行い、偵察を自動化し、弱点を見つけ、通常のビジネス活動に溶け込むことができる今、このことは特に重要です。同時に、組織とその従業員はAIを活用したイノベーションを進めており、そのことがアタックサーフェスをさらに広げ、新たなリスクをもたらしています。防御者は、こうした複雑な環境に対応し、安全で透明性があり、レジリエンスの強化に役立つAIを必要としています。また、組織全体でAIを安全に導入し、管理し、防御する方法が必要です。

OpenAI Daybreakサイバーパートナープログラムへの参加は、その方向へのさらなる一歩です。私たちはまだこの作業の初期段階にあり、慎重かつ規律あるアプローチで取り組んでいます。ただ、方向性は明確です。組織を守るには、攻撃だけでなくビジネスを理解するAIが必要です。

ダークトレースでは、まさにその点に重点をおいており、OpenAIとのこのパートナーシップに大きく期待しています。

[related-resource]

Continue reading
About the author
あなたのデータ × DarktraceのAI
唯一無二のDarktrace AIで、ネットワークセキュリティを次の次元へ