THQ Nordic targeted by Direwolf ransomware gang
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 THQ Nordic with exfiltration of employee credentials and data.
Direwolf ransomware gang has publicly claimed responsibility for compromising THQ Nordic, a video game publisher and developer. According to public listings on ransomware.live, the threat actors claim to have exfiltrated data including credentials for 254 user accounts and 2 third-party employee accounts, along with details of 44 external-facing systems. The compromise indicates either successful credential theft via infostealer malware or direct exploitation of exposed assets. Defenders at THQ Nordic and organizations with business relationships to the company should assume credential compromise and monitor for lateral movement attempts, data exfiltration, and potential destructive payloads. The listing suggests data exfiltration prior to encryption, which is typical for double-extortion ransomware operations.
Mentioned in this report
Detection guidance
Kubernetes Service Account Token or Secrets Read via Command Line
Detects command-line reads of the Kubernetes service account token or direct queries of the Kubernetes API secrets endpoint, a container credential-theft pattern. 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: Kubernetes Service Account Token or Secrets Read via Command Line
description: Detects processes reading the mounted Kubernetes service account token
or querying the Kubernetes API secrets endpoint with curl/wget/kubectl from a host
or container. Generic container credential access behaviour; the report gives no
command-level detail, so this rule is based on the mapped technique T1552.007.
tags:
- attack.credential-access
- attack.t1552.007
logsource:
category: process_creation
product: linux
detection:
selection_token_read:
Image|endswith:
- /cat
- /curl
- /wget
- /base64
- /head
- /tail
- /less
- /more
CommandLine|contains: /secrets/kubernetes.io/serviceaccount/
selection_api_secrets:
Image|endswith:
- /curl
- /wget
CommandLine|contains|all:
- /api/v1/
- secrets
selection_kubectl:
Image|endswith: /kubectl
CommandLine|contains:
- get secret
- get secrets
condition: 1 of selection_*
falsepositives:
- Cluster administrators running kubectl get secrets for troubleshooting from a jump
host or pod
- In-pod health or bootstrap scripts that read the service account token to call the
API
level: medium
id: 4ade0b7f-4c80-556b-a530-a47e9bbcb27b
status: experimental
author: Vorant
references:
- https://www.ransomware.live/id/VEhRIE5vcmRpY0BkaXJld29sZg==
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/VEhRIE5vcmRpY0BkaXJld29sZg==
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