VirusTotal has rolled out a ransomware detection update that checks whether suspicious files actually encrypt user documents during execution.
The new checks caught a Python ransomware sample that recorded zero detections across 75 antivirus engines at the time of analysis, showing how behavior checks can expose threats that static scanning misses.
The update spans VirusTotal and Google Threat Intelligence, adding verified encryption tags, stricter ransomware behavior rules, and support for real-time hunting. Rather than treating encryption code or heavy file activity as proof of ransomware, the system looks for damage to user documents inside controlled test environments.
The new tag:encrypts-files search tag and behaviour_tags:encrypts_files behavior trait work across CAPE Sandbox and Zenbox on Windows, plus macOS Mirage on Apple Silicon. VirusTotal introduced macOS Mirage to provide native Apple Silicon malware analysis and detailed behavior reports.
High-level overview of CAPE Sandbox, Zenbox, and macOS Mirage verifying file encryption before tagging T1486.(source : virustotal )
Each environment contains realistic user documents. During and after execution, the sandboxes inspect changed files for broken document structures, unusual byte patterns, and higher data randomness. These checks examine the results on disk instead of relying only on calls to operating system encryption tools.
VirusTotal Ransomware Detection Missed
That approach covers malware using built-in AES, ChaCha20, XOR, or partial encryption routines. Such variation matters because ransomware families use different methods to damage files, as seen in Beast ransomware’s partial encryption design.
The sandboxes also track linked file reads, writes, renames, and deletions. The sandbox excludes routine installer activity, browser caches, and temporary files. A ransom note or encryption function alone does not trigger the tag.
The standout example is system_update.pyw, a Python locker linked to a .k404 extortion campaign submitted on November 17–18. Although its static scan showed 0/75 detections, Zenbox observed it running through pythonw.exe, deleting itself, and rewriting Desktop documents into .k404 encrypted files.
Undetected Python locker encrypts Desktop files with the .k404 extension (T1486) (source : virustotal )
A related Windows program, K404T_Fidye.exe, had 10/75 detections. Another locker, lkd.exe, had just 3/75. CAPE confirmed that both encrypted user documents, providing evidence beyond their antivirus scores.
The checks also identified INC Ransom encrypting documents.INC files and dropping INC-README.txt ransom notes. INC has previously appeared in healthcare attacks linked to Vanilla Tempest, underlining the value of clear encryption evidence during investigations.
VirusTotal reports that the tag matched 55 files among 328,257 newly submitted unique files analyzed since November 17. Manual review found no benign software among those matches. These early results do not establish that future scans will have no false positives.
CAPE also tightened its mapping to MITRE ATT&CK T1486, Data Encrypted for Impact. Generic file activity now requires verified document encryption before receiving that mapping. VirusTotal says the change reduced false-positive T1486 volume across the platform by 97.6%.
INC Ransom encrypts user files with the .INC extension (T1486 ) (source : virustotal )
Analysts can search entity: file tag:encrypts-files or use VirusTotal Livehunt with the YARA-X trait vt.BehaviourTrait.ENCRYPTS_FILES for real-time alerts. Adding a low antivirus detection threshold helps focus hunts on overlooked samples.
A missing tag, however, is not a clean verdict. Malware may need passwords, user input, network access, or more time before it starts encrypting. The feature confirms observed file encryption, not the absence of ransomware when a sandbox run shows none.
Analysts should also remember that the reported 0/75 score describes the sample at analysis time, not a permanent detection result, and does not prove every endpoint product would fail to stop it.
Give your SOC the alert context on the latest threats to stop incidents quickly -> Integrate Threat Intel from 16K SOCs
——————————————————–
Click Here For The Original Source.
