File scan report
Verdict Safe
Is Mice
Zero engine detections, long-established prevalence, and no sandbox malice verdict outweigh the unsigned status and limited network evidence.
Read the whole reasonShow less
Strong evidence · Widely seen for a long time, and nothing harmful found.
The evidence supports treating the file as safe for normal use while maintaining standard security hygiene.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 72 flagged
- Flagged 0
- No detection 72
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 3y ago
Chapter 02
Why we think so
2 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
All 72 antivirus engines that checked it returned clean. The file has been submitted 266 times over nearly four years with no malicious labels. Sandbox runs showed no malicious verdict and files it created are clean. Unsigned status and incomplete host-reputation data are the only caveats.
Zero detections across major, smaller, and less reliable 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 files it created. 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 on Dec 24, 2022 and submitted 266 times by 241 distinct sources.
Threat Behavior
No sandbox verdict labeled the activity malicious, and no files it created were flagged. Host-reputation cross-check data is unavailable.
What To Do Now
Keep security software 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
- The missing contacted-host reputation result 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 files it created
- File is unsigned
- Direct-IP network traffic observed
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 11sandbox rule tags
- 3spawned processes
- 3network contacts
- 32filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
11MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1012
- T1055· Process injection
- T1057· Lists programs
- T1071· Application protocol
- T1082· System recon
- T1129· Loads modules
- T1497· Sandbox evasion
- T1518.001· Checks your AV
- T1542.003
- T1562.001· Disables security
- T1574.002· Execution hijack
Observed activity
Processes started
3Programs the file ran, with their command lines.
file.exe"C:\Users\<USER>\Desktop\file.exe"8a23962445f7647ef324b62b2ed58220334d345cec0ffbcd45bf2478bb823f0d.exe%SAMPLEPATH%\8a23962445f7647ef324b62b2ed58220334d345cec0ffbcd45bf2478bb823f0d.exeexecutable.exe"C:\Users\user\Desktop\executable.exe"
Network contacts
33 hosts, listed as 3 addresses. Links show the host and path only.
- IP address
23.216.147.78 - IP address
23.216.147.67 - IP address
23.53.122.199
Files
26Files the file created, changed or deleted.
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\46e6a289-7bc4-41f7-9aaf-a8203b9ccad6 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\23bd00f2-ae34-4dfd-9e5d-1aba9fca82f8 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\f3bba941-46fb-4f19-9f83-0883af8adcc5
Show all 26 entries for files
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp\d3225f37-c04c-4193-9d59-9e790c1e2790 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\842c44f3-51f3-4348-a048-83e3c2d116b6 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\b75ffad6-6fb4-4cf1-a71b-a2779d02a5c9 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WERAE41.tmp.dmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WERB7E7.tmp.WERInternalMetadata.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WERB94F.tmp.xml - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\8c58531d-d9af-424a-b278-79a2280b0f7a - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\54672a17-515d-4d42-93ec-73c001171145 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\5f8baea2-55a8-4d8a-bc30-d3a98b8d668d - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERAE41.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERB7E7.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERB94F.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERAE41.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERB7E7.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERB94F.tmp.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WEREA83.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WEREA83.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERF189.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERF189.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERF2E1.tmp
Registry and auto-start
1Settings the file changed, including ways to start again after a restart.
- Deleted
\REGISTRY\A\{cd4961f3-86ef-d77c-7896-4b6a4df8dfc8}\Root\InventoryApplicationFile\PermissionsCheckTestKey
Mutexes
6Named locks a program uses so only one copy runs; malware families often reuse them.
Local\WERReportingForProcess6804Global\AmiProviderMutex_InventoryApplicationFileGlobal\7e216ab7-999a-4bc1-8ff9-276e6ebd67b3\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6088\Sessions\1\BaseNamedObjects\Global\AmiProviderMutex_InventoryApplicationFile\Sessions\1\BaseNamedObjects\Global\d354cd47-99ed-4a5d-ad38-a29aa2533671
Sandbox background — not the file
13The analysis machine's own processes and connections, recorded in every run.
- VM process
WerFault.exeC:\Windows\system32\WerFault.exe -u -p 6804 -s 388 - VM process
WerFault.exeC:\Windows\System32\WerFault.exe - VM process
UI0Detect.exeC:\Windows\System32\UI0Detect.exe - VM process
updater.exeC:\Program Files\Google3180_737271696\bin\updater.exe - VM process
WerFault.exeC:\Windows\System32\WerFault.exe C:\Windows\system32\WerFault.exe -u -p 6088 -s 180 - VM host
a83f:8110:8d00:100:89:9598:0:8b
Show all 13 entries for sandbox background — not the file
- VM host
192.168.0.25 - VM host
184.27.218.92 - VM host
a83f:8110:0:0:1b00:100:2800:0 - VM host
192.168.0.17 - VM host
20.69.140.28 - VM host
23.196.145.221 - VM host
20.99.133.109
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache. 2 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 1aa28b51c33362384d15…d25c6cNot checkedno saved verdict
- 8e19bc6ccdb8c6342623…dbae96Not checkedno saved verdict
Chapter 04
Technical details
None of the 72 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Sep 3, 2026, 7:30 AM UTC
- SHA-256
8a23962445f7647ef324b62b2ed58220334d345cec0ffbcd45bf2478bb823f0d- SHA-1
65557c4a526e7defab879084e529ee503f7ea539- MD5
173da4cf421d4af0e0d8fb98e4f85fbf
About this file
MiceTea.exe is a Win32 EXE file of 228.4 kB.
- Type and size
- Win32 EXE · 228.4 kB
- Signer
- UnsignedNo code signature.
- First seen
- Dec 24, 2022On VirusTotal.
- Submitted by
- 241 distinct sources
- Packer
- None detected
- Entropy
- 6.11 of 8
First scanned
Antivirus consensus
0 of 72 engines flagged this file
4 of the 76 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-236 engines0flagged
- Low-trust18 engines0flagged
View all 76 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BaiduClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
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.