REDLINE
.NET STEALER
PROFILING
STAGING
DetectionBlue TeamSOCOctober 12, 2026•9 min read

Detecting RedLine Stealer: TTPs and Host Behaviours

RedLine’s builds, packers and servers change constantly. Its job does not, and the job is what we detect.

Scroll

RedLine is a .NET infostealer sold as malware-as-a-service and delivered through cracked software, malvertising and loader chains. Law-enforcement action against RedLine and its sibling META infrastructure in 2024 did not erase the code that was already in circulation. We do not list hashes or servers here, because they churn within days. Instead we cover the behaviours public analyses consistently document.

Signals at a Glance

BehaviourWhereATT&CK
Browser credential, cookie and autofill stores read by an unsigned processEDR file access, 4663T1555.003
Crypto wallet, VPN client and FTP client configuration files collectedEDR file accessT1005
System profiling: hardware, installed software and security products via WMIEDR, ETW WMI-ActivityT1082
Security product enumerationWMI telemetry, EDRT1518.001
Screenshot captured and bundled with collected dataEDRT1113
Collected data sent to a hard-coded server, then the binary removes itselfNetwork, process creationT1041

Host Behaviours to Hunt

RedLine is a managed .NET assembly, so it commonly appears as a process running from a user-writable path or injected into a trusted .NET host. The collection phase touches many unrelated applications in a short window, which is the pattern to hunt. Start with the staging artifact, since Chromium locks the live database and stealers copy it:

// Microsoft Defender (KQL) - credential store copies created by a non-browser process
let Browsers = dynamic(["chrome.exe","msedge.exe","firefox.exe","brave.exe","opera.exe"]);
DeviceFileEvents
| where ActionType in ("FileCreated","FileRenamed")
| where FileName in~ ("Login Data","Cookies","Web Data","logins.json","key4.db")
| where InitiatingProcessFileName !in~ (Browsers)
| where FolderPath !has "\\User Data\\" and FolderPath !has "\\Profiles\\"
| project Timestamp, DeviceName, AccountName, FolderPath, FileName,
          InitiatingProcessFileName, InitiatingProcessFolderPath
// tune/validate: exclude backup, migration and EDR agents

Cleanup and Self-Deletion

After exfiltration the sample typically deletes itself with a delayed shell command. That short-lived cmd.exe child, spawned by a process in a user-writable path, is a useful second signal when the collection phase was missed:

title: Delayed Self-Deletion by Binary in User-Writable Path
logsource:
  category: process_creation
  product: windows
detection:
  selection_parent:
    ParentImage|contains:
      - '\AppData\'
      - '\Temp\'
      - '\Users\Public\'
  selection_cmd:
    Image|endswith: '\cmd.exe'
    CommandLine|contains:
      - 'timeout'
      - 'ping'
      - 'choice'
    CommandLine|contains|all:
      - 'del'
  condition: selection_parent and selection_cmd
level: medium
# tune/validate: installers and updaters self-delete; allowlist signed publishers
Vetted sources

Use vendor and CERT write-ups on RedLine for behaviour descriptions, the MITRE ATT&CK software page for RedLine Stealer, SigmaHQ and Elastic rules for credential access and self-deletion, and Splunk ESCU analytics. We deliberately omit indicators; take current ones from a live, vetted feed and baseline your own environment.

Build Detections That Fire

Mjolnir Security helps blue teams turn threat intelligence into high-fidelity detections across endpoint, network, identity and cloud telemetry.

Detection EngineeringManaged Detection & ResponseThreat HuntingIncident ResponsePurple Teaming
  • Detection Engineering We build and tune detections mapped to ATT&CK from your own telemetry.
  • Threat Hunting as a Service Hypothesis-driven hunts for the behaviours on this page.
  • 24/7 Incident Response Containment when a detection fires. Call +1 833 403 5875.
Written by: Mjolnir Threat Research (MTAC)  |  Published: October 12, 2026  |  Last reviewed: October 12, 2026