S0560: TEARDROP
MITRE ATT&CK S0560: TEARDROP Malware details for Windows, with detection guidance, relationships and mapped CVEs.
Security context for executives and security teams
TEARDROP matters because it is described by ATT&CK as a Windows, memory-only dropper observed during SolarWinds Compromise investigations. For leaders, the key issue is not just this specific malware name; it is whether the organization can investigate stealthy second-stage activity that may leave limited file evidence and may rely on registry activity, service abuse, obfuscation, and in-memory execution patterns.
Executive priority
Prioritize TEARDROP as a readiness test for high-consequence intrusion response: can security teams prove what happened on Windows systems when malware is memory-only, tied to a major supply-chain campaign, and associated with APT29 in ATT&CK reporting? Executives should ask whether endpoint telemetry, registry/service auditing, incident response retention, and historical investigation procedures are sufficient to support confident decisions during a supply-chain or advanced intrusion investigation.
Technical view
ATT&CK provides no official detection text for TEARDROP, so SOC and IR teams should validate coverage through the related behaviors: Query Registry, Modify Registry, Windows Service creation or modification, Obfuscated Files or Information, Deobfuscate/Decode Files or Information, and naming or placement that matches legitimate resources. Because the malware is described as memory-only and Windows-based, teams should not rely only on file-based detections; they should confirm endpoint visibility into process behavior, service configuration changes, registry access/modification, and suspicious in-memory execution indicators.
Likely telemetry
- Windows endpoint detection and response telemetry
- Process execution and parent/child process context
- Windows Registry query and modification events
- Windows service creation, modification, and configuration-change events
- Command-line and script execution logs where available
Detection direction
- Validate detections for unusual registry querying and registry modification on Windows hosts, especially when paired with suspicious process or service activity.
- Tune monitoring for new or modified Windows services, including service path changes and service names or locations that resemble legitimate resources.
- Review whether obfuscation and deobfuscation behaviors are detected behaviorally rather than only by static file signatures.
- Test investigation workflows for memory-only malware scenarios where disk artifacts may be limited.
- Use the SolarWinds Compromise and APT29 relationships as threat-intelligence context, not as proof of current activity in the local environment.
Mitigation priorities
- Strengthen Windows endpoint visibility before relying on malware-name detection, since ATT&CK provides no TEARDROP-specific detection guidance.
- Limit and monitor permissions that allow service creation, service modification, and sensitive registry changes.
- Maintain change-control evidence for legitimate service and registry modifications to support faster triage.
- Ensure incident response playbooks include volatile-data and endpoint-timeline collection for memory-only malware investigations.
- For organizations with SolarWinds-related historical exposure or response obligations, preserve and review relevant host telemetry and investigation records where available.
Additional notes and limits
The strongest decision value is to treat TEARDROP as a coverage and response-readiness scenario for stealthy Windows second-stage malware associated in ATT&CK with the SolarWinds Compromise and likely APT29 use since at least May 2020. The relationship-mapped techniques provide the practical detection anchors: registry activity, service abuse, obfuscation/deobfuscation, and legitimate-looking resource naming.
ATT&CK does not provide official detection guidance, malware tactics, aliases, or detailed procedure steps in the supplied fields. This take does not assert active exploitation, local exposure, or guaranteed detection. Local endpoint telemetry, historical SolarWinds investigation scope, and asset context are required to determine relevance and coverage.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
TEARDROP
No official description is available in the imported ATT&CK source object.
How security teams should use this page
Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.
All related ATT&CK context
No relationships are available in the current normalized data for this object.
Object version and sync metadata
The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates.
Mirrored ATT&CK source object
The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.
Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.