Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Inhibit System Recovery (T1490): Detection and Defense

MITRE ATT&CK lists Inhibit System Recovery as T1490 under Impact.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
Abstract protected recovery path beside a fading backup path

An attacker may remove backups, delete snapshots, or disable recovery services to make restoration harder. The technique can precede Data Encrypted for Impact (T1486), but it is a separate action.

How it works

MITRE says T1490 can remove local recovery features, connected backups, ESXi snapshots, or cloud backup versions. The common effect is loss of a usable restore path. That differs from Data Encrypted for Impact (T1486), which concerns making data unavailable through encryption. The ransomware glossary entry explains the broader extortion context.

T1490 Inhibit System Recovery: Early Warning Signs

Kaspersky’s November 2026 ESXi and vCenter case shows why timing matters. Its investigators reported that backup services stopped and recovery infrastructure was encrypted before the final ESXi impact. That sequence is evidence from one case, not a pattern to assign to every ransomware operation. Review backup service state alongside vCenter tasks and host changes. A service stop just before a privileged virtualization change merits prompt investigation.

Brandefense’s ransomware intelligence page describes its related product. Brandefense Blackhole recorded 86 dark chat posts tagged Inhibit from 18 August to 16 November 2026. This is a count of posts, not incidents or proof of active exploitation.

A real example

MITRE lists Akira software (S1129) as a T1490 procedure example and says it deletes system volume shadow copies. In a separate ESXi and vCenter investigation, Kaspersky mapped disruption of backup services and recovery infrastructure to T1490 before production impact. Kaspersky says ransom notes identified the attacker as BlackNevas; that note is the stated basis for the name, not independent proof of operator identity. The Akira malware profile is linked only for MITRE's software example.

Who uses it

How to detect

  1. Review recovery feature changes

    MITRE DET0329 AN0933 looks for process activity that deletes shadow copies, removes backup catalogs, or disables recovery. Join process and service records with the affected host and change window.

  2. Alert on ESXi snapshot loss

    MITRE DET0329 AN0935 identifies ESXi shell activity or host events that delete VM snapshots. Compare the host and target VM with approved maintenance before treating the deletion as routine.

  3. Correlate cloud backup policy changes

    MITRE DET0329 AN0937 joins disabled snapshot schedules, backup policies, or versioning with later deletion events. Review the calling identity, affected resource, and approved change record.

  4. Join backup stops to hypervisor changes

    Kaspersky identifies backup service stops or disabled security controls shortly before hypervisor changes as a high priority signal. Correlate backup telemetry with vCenter Events and Tasks.

How to defend

  1. Keep a separate backup copy

    MITRE M1053 recommends backups kept off system and protected from the access an attacker may use to destroy primary copies. For ESXi, retain VM disk images and snapshots with copies stored away from the host.

  2. Separate recovery administration

    Kaspersky recommends independent backup administrator identities, isolated repositories, and restricted management paths. A production identity compromise should not grant control of the recovery environment.

  3. Test restoration without production control

    Kaspersky recommends testing a restore when vCenter and production directory services are unavailable. Verify that a clean operator can authenticate, reach the copy, validate it, and restore a workload.

  4. Restrict destructive access

    MITRE M1018 advises limiting backup access to required accounts. Apply approvals and monitoring to changes that can delete snapshots, disable versioning, or stop recovery services.

Frequently Asked Questions

Which ATT&CK tactic includes T1490?

MITRE places Inhibit System Recovery (T1490) under Impact. It covers actions that remove or disable ways to restore a system.

How is T1490 different from T1486?

T1490 targets recovery options such as backups and snapshots. T1486 covers encryption that makes data unavailable. MITRE says T1490 can increase the effect of T1486.

What is an early ESXi warning sign?

Kaspersky recommends correlating backup service stops or disabled security controls with later hypervisor changes. MITRE also lists ESXi snapshot deletion in DET0329.

Sources

  1. Inhibit System Recovery, Technique T1490MITRE ATT&CK
  2. Behavioral Detection for T1490, DET0329MITRE ATT&CK
  3. Ransomware at the hypervisor layer: how attackers use ESXi and vCenter features for malicious purposesKaspersky Securelist
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →