Skip to navigation

Threat reportRansomwareTL-2026-2074

Ransom Busters — Rogue ransomware affiliate posing as recovery firm to intercept ransom payments

highACTIVE

A suspected ransomware affiliate operating as 'Ransom Busters' contacts ransomware victims before attacks become public, offering decryption keys and stolen data deletion for $20,000–$60,000. GuidePoint Security GRIT assesses with moderate confidence that this is a single affiliate using their access to steal ransom payments from the RaaS operations they work with (DragonForce, Settra, Anubis).

Key facts

IdentifiersTL-2026-2074
SeverityHIGH
AttributionRansom Busters (medium confidence)
Malwareanubis
ToolsAnubis RaaS, DragonForce RaaS, Remotely RMM, Settra RaaS, SoftPerfect Network Scanner, s5cmd
MITRE ATT&CK techniquesT1003 OS Credential Dumping, T1018 Remote System Discovery, T1021 Remote Services, T1046 Network Service Discovery, T1059 Command and Scripting Interpreter, T1071 Application Layer Protocol, T1078 Valid Accounts, T1133 External Remote Services, T1219 Remote Access Tools, T1490 Inhibit System Recovery, T1560 Archive Collected Data, T1567 Exfiltration Over Web Service and 3 more in the attack flow
MotivationFINANCIAL
Target sectorsmanufacturing, finance, health, technology, legal, government administration, consumer-services
Target regionsNorth America, Europe, Asia-Pacific
Detection rules9 (1 shown free)
Sources11 cited sources

Detection coverage

As of 2026-08-19, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2074 across Splunk SPL, Microsoft KQL and Sigma, covering 9 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Local Backdoor Account Creation and PowerShell Tool Deployment — Ransom Busters Post-Exploitation

Detects the creation of local accounts (EventCode 4720) followed by PowerShell process execution (EventCode 4688 or Sysmon EventCode 1) installing RMM tools or performing credential dumping within a 24-hour window. Ransom Busters creates backdoor local accounts with the known password Numlock!123 (T1078.003) on victim systems, then uses PowerShell (T1059.001) to deploy the Remotely RMM tool and execute credential-access tools like Mimikatz (T1003.001). This detection specifically monitors for account names matching the Ransom Busters pattern and correlates with subsequent PowerShell activity deploying Remotely_Service or executing s5cmd.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1078.003, T1059.001, T1003.001
  • Data sources: windows_security, windows_sysmon, windows_event_log_4720, windows_event_log_4688
  • Severity: critical
  • Confidence: high

Splunk SPL

index=windows_security sourcetype="WinEventLog:Security" EventCode=4720 TargetUserName!=Guest TargetUserName!=Administrator
| search TargetUserName!="*$"
| eval suspicious_account=if(match(TargetUserName,"^(admin|backup|support|helpdesk|temp)[0-9]*$"),1,0)
| search suspicious_account=1
| table _time, TargetUserName, SubjectUserName, ComputerName
| join max=0 type=inner _time span=24h [
    search index=windows_sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
    (Image="*\\powershell.exe" OR Image="*\\pwsh.exe") CommandLine="*Remotely*" OR "*s5cmd*" OR "*netscan*" OR "*Invoke-Mimikatz*" OR "*procdump*" OR "*lsass*"
    | rename Computer as SysmonComputer
    | table _time, Image, CommandLine, SysmonComputer
]
| eval correlation_window="24h"
| table _time, TargetUserName, SubjectUserName, ComputerName, Image, CommandLine, correlation_window

Microsoft KQL

let AccountCreation =
    SecurityEvent
    | where TimeGenerated > ago(30d)
    | where EventID == 4720
    | where TargetUserName !in ("Guest", "Administrator")
    | where TargetUserName !endswith "$"
    | extend IsSuspicious = iif(TargetUserName matches regex @"^(admin|backup|support|helpdesk|temp)[0-9]*$", true, false)
    | where IsSuspicious == true
    | project AccountCreationTime=TimeGenerated, TargetUserName, SubjectUserName, AccountCreationComputer=Computer;
let ToolDeployment =
    DeviceProcessEvents
    | where TimeGenerated > ago(30d)
    | where FileName in~ ("powershell.exe", "pwsh.exe")
    | where ProcessCommandLine has_any ("Remotely", "s5cmd", "netscan", "Invoke-Mimikatz", "procdump", "lsass")
    | project ToolDeployTime=TimeGenerated, DeviceName, FileName, ProcessCommandLine;
AccountCreation
| join kind=inner (
    ToolDeployment
) on $left.AccountCreationComputer == $right.DeviceName
| where ToolDeployTime between (AccountCreationTime .. (AccountCreationTime + 24h))
| project AccountCreationTime, TargetUserName, SubjectUserName, AccountCreationComputer, ToolDeployTime, FileName, ProcessCommandLine
| order by AccountCreationTime desc

Sigma

title: Local Backdoor Account Creation Correlated with PowerShell Tool Deployment
id: e1b6c4d5-7f0a-4e4b-9c6d-0a5b8f9e4c3d
status: experimental
description: Detects the creation of local user accounts with suspicious naming patterns followed by PowerShell tool deployment within a 24-hour window. The Ransom Busters affiliate creates backdoor local accounts (T1078.003) with the known password Numlock!123, then uses PowerShell (T1059.001) to deploy Remotely RMM for persistent access, s5cmd for cloud exfiltration, and credential-dumping tools like Mimikatz or ProcDump targeting LSASS (T1003.001).
references:
    - https://www.cybereason.com/blog/threat-analysis-report-dragonforce-ransomware
    - https://attack.mitre.org/techniques/T1078/003/
    - https://attack.mitre.org/techniques/T1059/001/
    - https://attack.mitre.org/techniques/T1003/001/
author: Threadlinqs Team
date: 2026-08-19
tags:
    - attack.persistence
    - attack.execution
    - attack.credential-access
    - attack.defense-evasion
    - attack.t1078.003
    - attack.t1059.001
    - attack.t1003.001
logsource:
    product: windows
    service: security
    category: account_management
detection:
    selection_account:
        EventID: 4720
        TargetUserName|re: ^(admin|backup|support|helpdesk|temp)[0-9]*$
    condition: selection_account
    timeframe: 24h
    correlation:
        - PowerShell execution with Remotely, s5cmd, netscan, or credential-dumping tool references
falsepositives:
    - IT department creating standardized local accounts during system imaging or deployment
    - Authorized RMM tool deployment by corporate IT during incident response or maintenance windows
    - Password auditing tools that create test accounts with similar naming patterns
level: critical

Known false positives:

  • Authorized RMM tool deployment by corporate IT during maintenance windows or incident response
  • System imaging processes that create standardized local accounts during provisioning

Tuning notes: Tune the account-name regex to exclude your IT department's legitimate naming conventions. Correlate account creation events with the specific password hash for Numlock!123 (when available from Active Directory audit or local SAM monitoring). Extend the correlation window to 48h if tool deployment is delayed. Monitor for simultaneous account creation across multiple systems as a stronger indicator of coordinated adversary activity.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Anomalous External Remote Services Authentication via Valid Accounts — Ransom Busters · unlock with TL Creds
  • Credential Dumping via ProcDump or Mimikatz with Remotely RMM Staging — Ransom Busters · unlock with TL Creds
  • Remotely RMM Service Installation and SignalR Hub Connection — Ransom Busters C2 · unlock with TL Creds
  • Remote Desktop Protocol Logon with Attacker Hostname or Backdoor Account — Ransom Busters · unlock with TL Creds
  • s5cmd Cloud Storage Exfiltration and Data Archiving — Ransom Busters · unlock with TL Creds
  • SoftPerfect Network Scanner and Multi-Tool Lateral Movement Preparation — Ransom Busters · unlock with TL Creds
  • Suspicious External RDP Logon from Known Attacker Hostname — Ransom Busters Initial Access · unlock with TL Creds
  • SMB Lateral Movement and Service Execution via Admin Shares — Ransom Busters Lateral Movement · unlock with TL Creds

Indicators of compromise

As of 2026-08-19, Threadlinqs Intelligence tracks 9 indicators of compromise for TL-2026-2074.

Sample indicators (2 of 9)

  • Domain: protonmail[.]com
  • URL: hxxps://github[.]com/immense/Remotely

Defanged, TLP:CLEAR. Full set of 9 indicators: unlock with TL Creds.

9 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

The scheme represents a significant escalation in third-party ransomware interference, eroding the traditional 'pay and decrypt' model by introducing an uncontrollable third party with access to victim data.

Ransom Busters is a fraudulent persona that contacts organizations hit by ransomware, claiming to have breached the administrative panels of the ransomware-as-a-service (RaaS) operations that attacked them. The group offers to permanently delete stolen data from ransomware group servers and provide decryption keys in exchange for $20,000 to $60,000 in Bitcoin, requesting contact with the victim's CEO or IT leadership via ProtonMail. GuidePoint Security's GRIT (Research and Intelligence Team) identified this activity through incident response engagements where the same anomalous tooling, infrastructure, and credentials appeared across two separate ransomware incidents involving different RaaS operations.

GRIT found that the attacker used identical tooling — SoftPerfect Network Scanner for network reconnaissance, s5cmd for high-performance S3-compatible cloud storage exfiltration, and Remotely (an open-source .NET remote monitoring and management tool) for persistent remote access — across incidents involving DragonForce, Settra, and Anubis ransomware. Critically, the same local backdoor account password (Numlock!123) and attacker-controlled hostname (DESKTOP-BBETH6K) appeared in both incidents, strongly indicating a single operator. GRIT assesses with moderate confidence that Ransom Busters is not a legitimate third party but rather a ransomware affiliate 'using its access to steal ransom payments from the ransomware gangs it works with,' effectively double-dipping by collecting both the RaaS affiliate commission and direct victim payments.

Coveware, a ransom negotiation and incident response firm, confirmed responding to at least one such incident where the group contacted the victim via email claiming access to both the decryption key and stolen data. Coveware distinguishes this from traditional 'ambulance chaser' recovery scams that only contact victims after public disclosure — Ransom Busters' pre-public knowledge is 'much more concerning' because paying the original ransomware operator no longer guarantees that all parties with access to the data will honor a non-disclosure agreement.

The scheme creates a trilemma for victims: pay the RaaS gang, pay Ransom Busters, or neither — with no guarantee that any party will not still leak the data. Ransom Busters claimed to have been 'breaking into the servers for over three years' and justified their fees by stating that 'acting without compensation would put their access to the threat actor's infrastructure at risk.' GRIT's principal consultant Justin Timothy noted that the possibility of a legitimate organization is 'extremely unlikely' as it would violate the U.S. Computer Fraud and Abuse Act (CFAA). At the time of publication, no confirmed victims had paid Ransom Busters, and GRIT actively discourages payment to any criminal party.

MITRE ATT&CK techniques by tactic:

Credential Access

T1003 OS Credential Dumping

Discovery

T1018 Remote System Discovery; T1046 Network Service Discovery

Lateral Movement

T1021 Remote Services

Execution

T1059 Command and Scripting Interpreter; T1569 System Services

Command and Control

T1071 Application Layer Protocol; T1219 Remote Access Tools

Initial Access

T1078 Valid Accounts

Persistence

T1078 Valid Accounts; T1133 External Remote Services

Defense Evasion

T1078 Valid Accounts

Impact

T1490 Inhibit System Recovery; T1657 Financial Theft

Collection

T1560 Archive Collected Data

Exfiltration

T1567 Exfiltration Over Web Service

defense-impairment

T1685 Disable or Modify Tools

Remediation

Immediate actions

  • Engage a vetted incident response firm through established channels — do not respond to unsolicited recovery offers
  • Contact law enforcement (FBI IC3, CISA, local cybercrime unit) immediately upon receiving unsolicited recovery offers
  • Do not make payments to any party claiming to have decryption keys or stolen data without independent verification
  • Preserve all email communications from Ransom Busters for forensic analysis and law enforcement investigation

Workarounds

  • Restrict outbound S3/cloud-storage API access from internal systems to prevent s5cmd exfiltration
  • Block unauthorized RMM tools via application control policies
  • Audit local account creation and monitor for suspicious privileged account activity

Longer-term hardening

  • Implement robust incident response playbooks that include verification procedures for third-party recovery offers
  • Establish pre-vetted incident response retainer agreements with trusted firms before incidents occur
  • Deploy EDR with behavioral detection for RMM tools, network scanners, and cloud storage CLI tools
  • Monitor for known IOCs: backdoor password Numlock!123, hostname DESKTOP-BBETH6K, s5cmd/Remotely/SoftPerfect execution
  • Implement application allowlisting to block unauthorized RMM tools and cloud storage CLIs

Timeline

  • Coveware first encounters 'middlemen' contacting ransomware victims before public disclosure, using various aliases
  • Anubis ransomware first appears under the test name 'Sphinx' before rebranding, later recruiting affiliates on RAMP and XSS forums
  • DragonForce launches formal affiliate program on Russian-language RAMP forum, offering 80/20 revenue split and white-label RansomBay leak site service
  • Settra ransomware first publicly observed, posting victims on Tor-based leak site with investigative-style narratives
  • Coveware Q2 2026 report shows average ransom payment surged 176% to $1,880,612; median payment declined 50% to $150,000, driven by high-value data exfiltration extortions
  • Coveware publishes analysis of adverse cyber extortions, noting that LockBit takedown (Feb 2024) revealed retained stolen data despite deletion promises; Icarus/Klue supply chain compromise (June 2026) demonstrates payment does not guarantee data deletion
  • GRIT responds to multiple ransomware incidents where identical anomalous tooling, infrastructure, and credentials appear across DragonForce, Settra, and Anubis ransomware attacks
  • GuidePoint Security GRIT concludes with moderate confidence that Ransom Busters is a single ransomware affiliate using the persona to steal ransom payments from the RaaS operations they work with
  • BleepingComputer, Dark Reading, The Hacker News, Cybersecurity Times, and Cybersecurity Insiders publish coverage of the Ransom Busters scheme, warning the security community

Sources cited

Previous and next in ransomware

Drafted by the Threadlinqs research pipeline from 11 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats