VORANT. Threat Intelligence Research Sign in Create a free account

TOTVS targeted by Direwolf ransomware gang

elevated threat technology

Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.

Direwolf ransomware operators claim compromise of TOTVS with 491 compromised users and exposed attack surface.

Direwolf ransomware group has publicly claimed a compromise of TOTVS, a major Brazilian enterprise software company. The incident involved 52 compromised employees, 491 compromised user accounts, and 25 third-party employee credentials exposed. The attacker also identified 122 external attack surface elements on the victim's domain, suggesting either reconnaissance capability or post-compromise access to internal documentation. This represents a typical extortion-based ransomware operation where the threat actor leverages credential theft and reconnaissance data as leverage for ransom demands. The posting on ransomware.live indicates the group is pursuing public exposure tactics common to modern ransomware-as-a-service operations.

Mentioned in this report

Threat actors Dire Wolf
Malware Direwolf

Detection guidance

Network Packet Capture Started via Built-in or Common Sniffing Utilities

ATT&CK T1040

Detects packet capture started with netsh trace, pktmon, or command-line sniffers (tshark, dumpcap, windump, RawCap) on Windows hosts, which can be used for credential sniffing. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.

title: Network Packet Capture Started via Built-in or Common Sniffing Utilities
description: Detects initiation of packet capture on Windows using netsh trace, pktmon,
  or command-line sniffers such as tshark, dumpcap, windump and RawCap. Attackers
  use these to harvest credentials from network traffic. The report gives no concrete
  tooling, so this rule covers the generic technique pattern only, and baseline admin
  and helpdesk use before alerting.
tags:
- attack.credential-access
- attack.discovery
- attack.t1040
logsource:
  category: process_creation
  product: windows
detection:
  selection_netsh:
    Image|endswith: \netsh.exe
    CommandLine|contains|all:
    - trace
    - start
  selection_pktmon:
    Image|endswith: \pktmon.exe
    CommandLine|contains: start
  selection_tools:
    Image|endswith:
    - \tshark.exe
    - \dumpcap.exe
    - \windump.exe
    - \rawcap.exe
  condition: 1 of selection_*
falsepositives:
- Network or helpdesk engineers running netsh trace or pktmon for troubleshooting
- Security or QA teams running Wireshark/tshark on analyst or test workstations
level: medium
id: 3ee30094-cebe-53f9-a53c-42a0b1a2ea64
status: experimental
author: Vorant
references:
- https://www.ransomware.live/id/VE9UVlNAZGlyZXdvbGY=

1 more detection for this report is in the app — the rules that match its indicators, plus the Sigma rules already converted to Splunk SPL, to Elastic where their fields map onto Elastic's integrations and to Microsoft Defender XDR KQL wherever Defender records the activity, and the YARA and Suricata. Three days of it free, no card.

Behavioural rules are generated from public reporting — validate in your environment before deploying.

Source reporting: https://www.ransomware.live/id/VE9UVlNAZGlyZXdvbGY=

What this brief leaves out

This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.

It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.

A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.

Create a free account   What it costs