Is dimmer_v2.0.1.zip safe?
Zero detections across 73 engines, long-established prevalence, and no malicious children or host contacts.
All 73 engines returned clean results. The file is common and old with thousands of prior submissions. Sandbox noted process-injection and LSASS activity, but no engine or child-file evidence supports malice.
93e88dc2781adaf0c3…cc8cd31a4187b9Recommended next actions
Before opening or extracting
Open or extract it only when its sender or download source has been independently verified.
If you already opened or extracted it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
All 73 engines returned clean results. The file is common and old with thousands of prior submissions. Sandbox noted process-injection and LSASS activity, but no engine or child-file evidence supports malice.
The complete absence of malicious detections from every tier-1 and tier-2 engine outweighs the sandbox heuristics. Prevalence data shows the file has circulated for nearly four years without incident. No dropped child or contacted host carries a malicious verdict. The two triggered heuristics map observed behaviour to offensive techniques, yet lack corroboration from any engine or external intelligence source.
What We Detected
73 engines scanned the ZIP; none flagged it malicious or suspicious. Sandbox execution produced MITRE mappings T1055 and T1562.001 plus LSASS access, but returned no malicious verdict and no malicious child files.
Threat Behavior
The observed process activity is consistent with the heuristics, yet the file has been submitted 3729 times over 1372 days with zero engine detections and no external-intel hits.
What To Do Now
Keep endpoint protection enabled. The file can be treated as benign based on current evidence, but monitor any new submissions or behaviour changes.
Where this verdict could be wrong1 caveat
- Sandbox observed LSASS access and process-injection activity (T1055) which legitimate software rarely performs; however, no engine flagged the sample and no malicious child or host contact was recorded.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/73 engines flagged the sample
- common_old prevalence with thousands of prior submissions
- no malicious dropped children
- no external intelligence hits
- Sandbox observed LSASS access and process-injection techniques
The file shows no malicious indicators from engines or external sources; retain normal security settings and treat as safe.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 73 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 8MITRE ATT&CK techniques
- 15spawned processes
- 0network contacts
- 20filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
dimmer_v2.0.1.zip
93e88dc2781adaf0c3be9ebe4395d45c42ca96df5d433bdd6ecc8cd31a4187b9
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\Dimmer.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Dimmer.ini
C:\Users\<USER>\AppData\Local\Temp\Dimmer.ini
04Isolated runtime analysis - Written fileObserved
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
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.
- C:\Users\<USER>\AppData\Local\Temp\Dimmer.ini
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\Users\<USER>\Downloads\Dimmer.ini
- C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
- C:\Users\user\AppData\Local\Temp\04x5hw5i.xla
- Dimmer
- Local\__DDrawCheckExclMode__
- \Sessions\1\BaseNamedObjects\Dimmer
- \Sessions\1\BaseNamedObjects\Local\__DDrawExclMode__
- \Sessions\1\BaseNamedObjects\Local\__DDrawCheckExclMode__
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- deef1f698aa1dcea70d7…7eacb5Never scannednever seen before
- 3251630556d4979d5126…07d504Never scannednever seen before
- 7e19b6d0ff27ae200ebb…d215c2Never scannednever seen before
- 39d5127d3a79ca48c9ed…404b83Never scannednever seen before
- 23c960bed0677e68962e…e401d7Never scannednever seen before
- b7ba91f84e9c9ba9b498…43e887Never scannednever seen before
- 42dba24c92021b8ee37d…757736Never scannednever seen before
- 6da58632c733da5f9fb4…b93b5cNever scannednever seen before
- c7a9a74533116e6c21d1…334f30Never scannednever seen before
- 974bfd7772adb82ad155…ca9613Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 0 / 73engines flagged
- 2,900sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 73 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 2,900 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: dimmer_v2.0.1.zip — 93e88dc2781adaf0c3be9ebe4395d45c42ca96df5d433bdd6ecc8cd31a4187b9
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\Dimmer.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Dimmer.ini — C:\Users\<USER>\AppData\Local\Temp\Dimmer.ini
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exe
0 of 73 engines flagged this file
View all 73 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- dimmer_v2.0.1.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 55.3 KB
- Last analyzed
- Sep 3, 2026, 2:22 AM UTC
93e88dc2781adaf0c3be9ebe4395d45c42ca96df5d433bdd6ecc8cd31a4187b9Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Open or extract it only when its sender or download source has been independently verified.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is dimmer_v2.0.1.zip safe?
What is dimmer_v2.0.1.zip?
How many antivirus engines detected dimmer_v2.0.1.zip?
What is the SHA-256 hash of dimmer_v2.0.1.zip?
Is it safe to open or extract dimmer_v2.0.1.zip?
How up to date is this analysis of dimmer_v2.0.1.zip?
Community
Member reviews and reports for this exact file hash.