S1053: AvosLocker
MITRE ATT&CK S1053: AvosLocker Malware details for Linux, Windows, with detection guidance, relationships and mapped CVEs.
Security context for executives and security teams
AvosLocker matters because it represents ransomware behavior tied to direct availability risk on Windows and Linux environments. The ATT&CK relationships show more than encryption: discovery of files, processes, time, and network shares; stealth and masquerading; persistence via Windows Run Keys or Startup Folder; service stopping; reboot/shutdown activity; and Windows Safe Mode abuse that can weaken endpoint defenses. For leaders, this is a business continuity and incident readiness issue, not only a malware-signature issue.
Executive priority
Prioritize validation of ransomware resilience: recoverability of critical systems, visibility across Windows and Linux hosts, protection of shared storage, and response procedures for service disruption. Because the official ATT&CK description cites use against financial services, critical manufacturing, government facilities, and other critical infrastructure sectors as of 2022, organizations in operationally sensitive sectors should ensure ransomware tabletop exercises, backup evidence, and SOC escalation paths cover encryption, service stoppage, and endpoint defense impairment scenarios.
Technical view
SOC and IR teams should map AvosLocker-relevant coverage to the supplied ATT&CK relationships: obfuscated or masqueraded files, dynamic API resolution on Windows, native API use, process/file/network share discovery, deobfuscation behavior, encryption for impact, service stop, shutdown/reboot, Run Key or Startup Folder persistence, hidden windows, and Safe Mode boot abuse. MITRE provides no official detection text for this object, so validation should be behavior-led rather than dependent on a named malware analytic.
Likely telemetry
- Endpoint process creation and command-line telemetry on Windows and Linux
- File creation, rename, extension, header/magic-byte mismatch, and high-volume file modification telemetry
- Registry monitoring for Windows Run Keys and Startup Folder changes
- Service control events, including service stop or disable activity
- System shutdown, reboot, and boot configuration events, including Safe Mode indicators on Windows
Detection direction
- Validate behavior chains rather than single indicators: discovery of files/shares followed by service stoppage or high-volume file modification is more actionable than any one event alone.
- Tune for false positives from legitimate administration, backup tools, software deployment, and maintenance windows, especially for service stop, reboot, registry startup entries, and share enumeration.
- Confirm Windows-specific coverage for Run Keys/Startup Folder, dynamic API resolution-related detections where available, hidden window behavior, and Safe Mode boot attempts.
- Confirm Linux coverage is not limited to Windows ransomware assumptions; the object explicitly lists Linux and Windows platforms.
- Because official detection guidance is not provided, use the cited external references for indicators and enrich them with local behavioral analytics and incident findings.
Mitigation priorities
- Sequence controls around resilience first: tested offline/immutable backups, restoration evidence, and recovery priorities for critical services and shared data.
- Harden and monitor administrative paths that can stop services, reboot systems, alter startup locations, or enumerate shares.
- Ensure endpoint defenses and logging remain available after reboot scenarios and that teams can identify cases where security tooling fails to start, including Safe Mode-related conditions on Windows.
- Reduce blast radius through least privilege, segmentation around critical shares, and controlled access to high-value file repositories.
- Maintain incident response playbooks for ransomware impact behaviors: isolation, preservation of evidence, service restoration, and executive decision workflows.
Additional notes and limits
This take is based only on the supplied ATT&CK S1053 object, its official description, external references, and listed relationships. The most decision-relevant relationships are impact and defense-impairment behaviors: Data Encrypted for Impact, Service Stop, System Shutdown/Reboot, and Safe Mode Boot. The discovery and stealth relationships explain why early detection may depend on endpoint and file/share visibility before encryption becomes obvious.
MITRE does not provide official detection text, aliases, labels, or explicit tactics for the malware object itself in the supplied fields. Technique relationships provide behavioral context but do not prove those behaviors will occur in every incident. Local telemetry, asset criticality, backup architecture, and control configuration are required to determine actual exposure and coverage.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
AvosLocker
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.