Malicious
15 tier-1 antivirus engines converge on Tedy/DLLhijack trojan family; unsigned DLL with rundll32 proxy execution telemetry; 1,474 submissions confirm widespread malware.
ba740fc3f76464c5aa…8c3c1b3bc1The 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.
The evidence strongly indicates genuine malware. Tier-1 consensus (15/17 engines) with strong family agreement (5 engines on 'win64') is a hallmark of real malware detection, not false positives. Named families (Tedy, DLLhijack, Agent, Packunwan) from reputable engines like BitDefender, Kaspersky, Avira, and ESET rule out generic heuristic noise. The unsigned status and filename mimicking a legitimate Windows DLL (WINMM.dll) are consistent with DLL hijacking tactics. Process telemetry showing rundll32.exe proxy execution (T1218.011) and DLL side-loading (T1574.002) aligns with the threat label. High prevalence (1,236 submitters, 1,474 submissions) confirms this is a known malware sample, not a rare false positive.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
tier1Malicious=15/17 tier-1 engines; tier1FamilyConsensus.strong=true (5 engines agreeing on 'win64')
BitDefender, Kaspersky, Avira, ESET-NOD32, Sophos, Microsoft all flagging with named families (Tedy, DLLhijack, Agent, Packunwan)
Unsigned DLL mimicking legitimate Windows system file (WINMM.dll); behaviour shows rundll32.exe proxy execution (T1218.011) and DLL hijacking patterns
prevalence.classification='common_old' — 1236 submitters, 1474 submissions since June 2025; widely-known malware sample
No malicious sandbox verdict, no contacted malicious hosts, no dropped children — but tier-1 consensus and named families override absence of runtime telemetry
- No malicious sandbox verdict recorded (though sandbox execution occurred)
- No contacted malicious hosts in our URL cache
- No dropped malicious children detected
- No adversarial input flags or brand mismatch
- Tier-1 consensus: 15 of 17 tier-1 engines flagging as malware
- Named malware families: Tedy, DLLhijack, Agent, Packunwan across reputable engines
- Unsigned DLL mimicking legitimate Windows system file (WINMM.dll)
- DLL hijacking execution pattern: rundll32.exe proxy execution (T1218.011, T1574.002)
- High prevalence: 1,474 submissions from 1,236 sources since June 2025
- 64-bit trojan with potential for system-level compromise
This file is malware and should be removed immediately. Do not execute or open it under any circumstances. Perform a full system scan with updated antivirus software and consider professional incident response if this file was found on a production system.
dllhijack corroborated by 2 sources
- VT (75 engines)dllhijack
- MT AI EngineTedy
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- \Device\ConDrv\\Connect
- \Sessions\1\BaseNamedObjects\Local\SessionImmersiveColorMutex
51 detections across 75 engines
Section entropy & packers
Section-level entropy and packer detection from the PE header. Nothing suspicious here — entropy is within the normal range for unpacked code.
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
- WINMM.dll
- Size
- 16.31 MB
- MIME type
- (unknown)
- Detected type
- Win32 DLL
- SHA-256
- ba740fc3f76464c5aac4409f834f6dc910e5494132f957a28472fc8c3c1b3bc1
- MD5
- fc7f0cb1c8b54d65d49217bdcadd0acc
- SHA-1
- 79424b331629aa23e80ee02ac58665cd600da489
- PE imphash
- 98749fa3bd96823b0ff1ef9486650c7a
- First seen (VT)
- 6/23/2025, 2:26:43 PM
- Last analysis (VT)
- 5/30/2026, 10:43:49 PM
- First scan (MalwareTips)
- 6/28/2026, 11:30:24 AM
- Last scan (MalwareTips)
- 6/28/2026, 11:30:24 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.