Safe
Widely submitted RAR archive with zero engine detections and established prevalence.
d5c5bb2e7273e82581…82e2f1d3bbThe verdict, reasoned out.
Not a rules engine. The MT AI Engine reads every signal we collected, weighs them against history, and commits to an answer.
Zero malicious detections from 63 reporting engines including 17 tier-1 engines rules out any named family or hacktool consensus. The file is an unsigned RAR that has been submitted 184 times by 165 sources since late 2025, placing it in the common_old bucket. Filename analysis shows no security-software mimicry and no heuristics fired. Without sandbox execution data the runtime behaviour remains unknown, but the combination of age, volume, and clean engine results supports a safe classification.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines.malicious=0, tier1Malicious=0, reporting=63
prevalence.classification=common_old (165 uniqueSources)
signing.signed=false, filenameAnalysis.looksLikeSecuritySoftware=false
- Zero detections across tier-1 and tier-2 engines
- Established common_old prevalence
- No adversarial filename or injection flags
Treat as low-risk commodity archive; verify contents after extraction.
0 detections across 76 engines
How often this file shows up in the wild
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Forensic fingerprint
- File name
- MfW10_Fix_Repair_GDK_V6_Generic.rar
- Size
- 8.44 MB
- MIME type
- (unknown)
- Detected type
- RAR
- SHA-256
- d5c5bb2e7273e825814cb2fd7b392ac5768241dadb2ef04033fd3a82e2f1d3bb
- MD5
- dee620e541cc2f8617e3248bfbab1654
- SHA-1
- 613dcd060cfa8b37d22d9b5d741316870f455341
- First seen (VT)
- 12/9/2025, 7:23:17 PM
- Last analysis (VT)
- 12/10/2025, 12:07:31 AM
- First scan (MalwareTips)
- 7/8/2026, 10:31:05 AM
- Last scan (MalwareTips)
- 7/8/2026, 10:31:05 AM
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.