--- title: "VirusTotal encrypts-files Tag: Hunting Ransomware Better" url: https://playciso.com/blog/virustotal-encrypts-files-tag-ransomware-t1486 updated: 2026-11-21 section: Blog publisher: PlayCISO --- # VirusTotal encrypts-files Tag: Hunting Ransomware Better > VirusTotal's new encrypts-files tag confirms real file encryption in its sandboxes and cut T1486 noise 97.6%. Queries, a YARA-X rule and the limits. Source: https://playciso.com/blog/virustotal-encrypts-files-tag-ransomware-t1486 · Published: 2026-11-21 · Publisher: PlayCISO (https://playciso.com) Primary source: https://blog.virustotal.com/2026/11/catching-ransomware-introducing.html --- On 20 November 2026, VirusTotal added an **encrypts-files** behaviour tag that its sandboxes attach to a file only when they see it **actually encrypt user documents**. At the same time it tightened how the CAPE sandbox maps behaviour to MITRE ATT&CK **T1486** (Data Encrypted for Impact), cutting platform-wide T1486 volume by 97.6%. For ransomware triage and hunting, that turns a noisy technique label into a usable filter. **Who this is for:** SOC analysts, threat hunters and detection engineers who use VirusTotal, and leaders deciding how much to trust "ransomware" labels in sandbox reports. *Based on VirusTotal's own blog post by Karl Hiramoto. PlayCISO is not affiliated with VirusTotal or Google. Facts as published on 20 November 2026.* Confirmed vs not yet known **VirusTotal states:** the tag is live in production, emitted by CAPE Sandbox (Windows), Zenbox (Windows) and macOS Mirage (Apple Silicon); stricter T1486 gating applies to CAPE only; 55 of 328,257 new unique files matched since 17 November, with zero benign false positives among the 55 reviewed. **Not stated:** which VirusTotal plans can use the tag in Intelligence search, Livehunt or the API. Check your subscription before building a process around it. ## What changed - Verified, not guessed. The sandboxes inspect modified files on disk for destroyed file structure, raised entropy or non-text bytes, and correlate reads, writes, renames and deletes to spot coordinated extension changes. Installers, archives, caches and README (ransom-note) drops are excluded. VirusTotal calls it cipher-agnostic: it does not depend on hooking crypto APIs. - Less T1486 noise. In CAPE, generic file-churn signatures no longer map to T1486 unless user-file encryption is verified. CAPE-only daily T1486 hits on benign files went from 1,039 (78.5% of them with 0 antivirus detections) to 0. Platform-wide T1486 volume went from 7,238 to 171 files per day. - Early results. Matches included a Python locker with 0 of 75 static detections, a .k404 campaign, INC Ransom, BlackWizardLock and a native macOS Heartbreaker sample. ## How to use it Search queries, as published by VirusTotal: `entity:file tag:encrypts-files entity:file tag:encrypts-files type:peexe tag:64bits entity:file tag:encrypts-files NOT type:peexe entity:file tag:encrypts-files type:macho entity:file tag:encrypts-files p:10-` The last one (`p:10-`) finds confirmed encryptors that fewer than 10 antivirus engines detect: the ones static scanning is most likely to miss. The API-side equivalent is `behaviour_tags:encrypts_files`. A Livehunt rule built from the YARA-X fragments in VirusTotal's post (the rule name is ours): `import "vt" rule encrypts_files_low_detection { condition: for any trait in vt.behaviour.traits : ( trait == vt.BehaviourTrait.ENCRYPTS_FILES ) and vt.metadata.analysis_stats.malicious VirusTotal advises against adding a T1486 condition to such a rule: it "adds no precision" over the trait. ### In ransomware triage - Tag present: treat it as strong confirmation that the sample encrypts files, even with zero AV detections, and escalate the host accordingly. - Tag absent: it proves nothing. Look at why the sample might not have run fully (arguments, passwords, sleeps, a missing key server, share-only targeting) before calling it benign. - Old report: cached reports keep their historical tags. Reanalyse in the web UI or use Private Scanning to refresh; VirusTotal notes the API analyse endpoint refreshes static AV only unless the file is re-uploaded or detonated. ## Timeline | Date (2026) | What | Source | | --- | --- | --- | | 17 Nov | Start of the measurement window: tag matches counted from here (55 of 328,257 new unique files) | VirusTotal | | 20 Nov | VirusTotal announces encrypts-files and stricter T1486 mapping in CAPE | VirusTotal blog | ## What security leaders should do this week - Ask the SOC whether any triage step or SOAR playbook treats a VirusTotal T1486 hit as "ransomware confirmed". With this change the meaning of that hit moved; update the playbook to use the tag. - Have the threat-intel lead set up the low-detection Livehunt rule above (if your plan allows it) and route matches to the people who maintain endpoint blocklists. - Write down in the ransomware runbook that a missing tag is not a clean bill of health, with VirusTotal's list of reasons. - Re-check one recent suspected-ransomware sample: reanalyse it and see whether the tag appears. ## FAQ ### What is the VirusTotal encrypts-files tag? A behaviour tag VirusTotal introduced on 20 November 2026. CAPE Sandbox, Zenbox and macOS Mirage add it to a file only when dynamic analysis confirms that the sample really encrypted user documents in the sandbox. VirusTotal says it is cipher-agnostic: instead of hooking operating-system crypto APIs, the sandboxes inspect the modified files on disk and correlate file reads, writes, renames and deletes. ### How do I search VirusTotal for ransomware with the new tag? VirusTotal's examples are: entity:file tag:encrypts-files (everything), add type:peexe tag:64bits for 64-bit Windows executables, NOT type:peexe for non-PE samples, type:macho for macOS, and p:10- for encryptors with fewer than 10 antivirus detections. The API-side equivalent is behaviour_tags:encrypts_files. VirusTotal's post does not say which subscription tiers can run these searches, so check your plan. ### What changed with MITRE ATT&CK T1486 on VirusTotal? In CAPE, generic file-churn signatures no longer map to T1486 (Data Encrypted for Impact) unless encryption of user files is verified. VirusTotal reports CAPE-only daily T1486 hits falling "from 1,039/day (78.5% with 0 AV detections) to 0 on benign files", and platform-wide T1486 volume dropping from 7,238 to 171 files per day, a 97.6% reduction. Zenbox, Mirage and third-party sandboxes keep their own T1486 mappings. ### How accurate is the encrypts-files tag? VirusTotal says the tag matched 55 of 328,257 newly submitted unique files (405,469 including rescans) analysed since 17 November 2026, and that manual review of all 55 found zero benign false positives. Matches included a Python locker with 0 of 75 static detections, a .k404 campaign, INC Ransom, BlackWizardLock and a native macOS Heartbreaker sample. ### Why would ransomware not get the encrypts-files tag? VirusTotal lists the gaps: samples that need command-line arguments or a password; sandbox evasion, user-interaction gates and long sleeps; samples that must fetch a key from an unreachable server; DLLs that only encrypt from a named or ordinal export; encryptors that target only network shares or niche file extensions; executable infectors; safe simulators; and analysis timeouts. Cached reports keep their old tags until the file is reanalysed. ### Should I add a T1486 check to my YARA-X rule as well? No. VirusTotal advises against adding a T1486 condition to rules that already match vt.BehaviourTrait.ENCRYPTS_FILES, because it adds no precision over the trait. ## Practise it - [Ransomware readiness scorecard](/tools/ransomware-readiness-scorecard): what happens after a confirmed encryptor lands. - [Ransom note interpreter](/tools/ransom-note-interpreter): read the note the sample drops. - [Detection Lab](/tools/detection-lab) and [hunt plan review](/tools/hunt-plan-review): build the hunt around the tag. ## Sources - [VirusTotal blog: Catching ransomware, introducing encrypts-files and stricter MITRE ATT&CK T1486](https://blog.virustotal.com/2026/11/catching-ransomware-introducing.html) (20 Nov 2026) - [MITRE ATT&CK: T1486 Data Encrypted for Impact](https://attack.mitre.org/techniques/T1486/)