Is MiceTea.exe safe?
Zero engine detections, long-established prevalence, and no sandbox malice verdict outweigh the unsigned status and limited network evidence.
All 76 engines returned clean. The file has been submitted 266 times over nearly four years with no malicious labels. Sandbox runs showed no malicious verdict and dropped children are clean. Unsigned status and incomplete host-reputation data are the only caveats.
8a23962445f7647ef3…bf2478bb823f0dRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran 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 76 engines returned clean. The file has been submitted 266 times over nearly four years with no malicious labels. Sandbox runs showed no malicious verdict and dropped children are clean. Unsigned status and incomplete host-reputation data are the only caveats.
Zero detections across tier-1, tier-2, and low-trust engines removes the primary malware signal. The file's age and submission volume indicate it is commodity software rather than a recent threat. Sandbox execution produced no malicious verdict and no malicious children. The two offensive MITRE mappings are static-behaviour correlations only and lack corroboration from sandbox verdicts or external intel. Unsigned status prevents the benign-signed-installer rule, but the remaining evidence still supports a safe determination.
What We Detected
76 engines scanned the sample; none flagged malicious or suspicious code. The file is a 64-bit Windows executable first seen 1349 days ago and submitted 266 times by 241 distinct sources.
Threat Behavior
One sandbox recorded process-injection (T1055) and defense-evasion (T1562.001) techniques, plus direct-IP connections. No sandbox verdict labeled the activity malicious, and no dropped children were flagged. Host-reputation cross-check data is unavailable.
What To Do Now
Keep endpoint protection enabled. The file shows no current malicious indicators, but treat any unsigned executable with caution and verify its source before execution.
Where this verdict could be wrong1 caveat
- contactedHosts=null means no complete host-reputation result is available; direct-no complete contacted-host reputation result was available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections from 76 engines
- Long history of clean submissions
- No malicious sandbox verdict
- No malicious dropped children
- File is unsigned
- Direct-IP network traffic observed
- Process-injection techniques recorded in sandbox
The evidence supports treating the file as safe for normal use while maintaining standard security hygiene.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial11 runtime contacts were observed without a completed reputation cross-check.
YARA
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
- 11MITRE ATT&CK techniques
- 8spawned processes
- 11network contacts
- 32filesystem & 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
MiceTea.exe
8a23962445f7647ef324b62b2ed58220334d345cec0ffbcd45bf2478bb823f0d
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\WerFault.exe -u -p 6804 -s 388
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
46e6a289-7bc4-41f7-9aaf-a8203b9ccad6
C:\ProgramData\Microsoft\Windows\WER\Temp\46e6a289-7bc4-41f7-9aaf-a8203b9ccad6
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a83f:8110:8d00:100:89:9598:0:8b
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
192.168.0.25
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- a83f:8110:8d00:100:89:9598:0:8b
- 192.168.0.25
- 23.216.147.78
- 184.27.218.92
- a83f:8110:0:0:1b00:100:2800:0
- 192.168.0.17
- 23.216.147.67
- 20.69.140.28
- 23.196.145.221
- 23.53.122.199
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\46e6a289-7bc4-41f7-9aaf-a8203b9ccad6
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\23bd00f2-ae34-4dfd-9e5d-1aba9fca82f8
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERAE41.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERB7E7.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERB94F.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERAE41.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERB7E7.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess6804
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\7e216ab7-999a-4bc1-8ff9-276e6ebd67b3
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6088
- \Sessions\1\BaseNamedObjects\Global\AmiProviderMutex_InventoryApplicationFile
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 1aa28b51c33362384d15…d25c6cNever scannednever seen before
- 8e19bc6ccdb8c6342623…dbae96Never 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 / 76engines flagged
- 241sources 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 76 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 241 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: MiceTea.exe — 8a23962445f7647ef324b62b2ed58220334d345cec0ffbcd45bf2478bb823f0d
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\WerFault.exe -u -p 6804 -s 388
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 46e6a289-7bc4-41f7-9aaf-a8203b9ccad6 — C:\ProgramData\Microsoft\Windows\WER\Temp\46e6a289-7bc4-41f7-9aaf-a8203b9ccad6
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: a83f:8110:8d00:100:89:9598:0:8b — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 192.168.0.25 — Contact observed during runtime.
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.
Evidence"C:\Users\<USER>\Desktop\file.exe"The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidencea83f:8110:8d00:100:89:9598:0:8b · 23.216.147.78 · 184.27.218.92
0 of 76 engines flagged this file
View all 76 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
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
- MiceTea.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 223.0 KB
- Last analyzed
- Sep 3, 2026, 7:30 AM UTC
8a23962445f7647ef324b62b2ed58220334d345cec0ffbcd45bf2478bb823f0dSafety & 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
Run it only when it came from the developer's official site or another source you independently trust.
- 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 MiceTea.exe safe?
What is MiceTea.exe?
How many antivirus engines detected MiceTea.exe?
What is the SHA-256 hash of MiceTea.exe?
Is it safe to run MiceTea.exe?
How up to date is this analysis of MiceTea.exe?
Community
Member reviews and reports for this exact file hash.