File scan report
Verdict Safe
Is Simpsons
Only two less reliable engines raised generic alerts, while major antivirus engines and corroborating intelligence found no named malware family or confirmed hostile outcome.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
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
2 of 71 flagged
- Flagged 2
- No detection 69
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 18d ago
Chapter 02
Why we think so
4 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Only 2 of the 71 antivirus engines that checked it flagged this executable, and both were less reliable generic detections; all 17 reporting major antivirus engines were silent. The unsigned, recently observed file deserves ordinary caution because one sandbox mapped potentially offensive techniques, but no injected target, malicious sandbox verdict, hostile sample-generated contact, or confirmed malicious child was recorded.
The detection pattern is dominated by two generic less reliable alerts, with no major antivirus engines detection or family consensus. One completed sandbox run mapped and T1485, but it did not identify an injected process and supplied no malicious sandbox verdict. The recorded domain and IP are explicitly identified as analysis-machine background traffic, so they do not establish sample network behavior. No malware-specific YARA rules, MalwareBazaar match, packed code, persistence indicator, or confirmed malicious child corroborates the alerts. The principal uncertainty is provenance: the executable is unsigned, recently observed, and has no comparable historical samples.
What We Detected
Only 2 of the 71 antivirus engines that checked it raised alerts. APEX used a generic malicious label and Trapmine reported a low machine-learning score; both are less reliable detections, while no major antivirus engines flagged the file and no engine family consensus emerged.
Threat Behavior
One sandbox run mapped T1055 process injection and T1485 data destruction. However, it recorded no injected target, no persistence indicator, and no malicious sandbox verdict. The listed domain and IP were identified as analysis-environment background traffic rather than sample activity. One dropped file lacks a saved verdict, which is missing coverage rather than evidence against the parent.
What To Do Now
Obtain the executable from a trusted source and verify its expected hash or publisher information before running it. Keep security software enabled, and avoid execution on sensitive systems if the source cannot be established.
Where this verdict could be wrong3 caveats
- The executable is unsigned and only four days old, so its publisher and distribution history cannot be independently established.
- The sandbox mapped process injection and data destruction, although it recorded no injected target and issued no malicious verdict.
- APEX and Trapmine flagged the sample, but both detections are generic and come from less reliable engines.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- All 17 reporting major antivirus engines produced no detection.
- The only two alerts were generic labels from less reliable engines.
- The sandbox produced no malicious verdict and recorded no injected target or persistence.
- No malware-specific research rules or known malware-repository match corroborated the alerts.
- No packing or high-entropy code was identified, and no file it created was confirmed harmful.
- The executable is unsigned and has no established publisher history.
- It was first observed on Oct 8, 2026 and has limited submission history.
- One sandbox mapped possible process injection and data-destruction techniques, although neither produced a confirmed hostile outcome.
- Two less reliable engines raised generic alerts.
6 sources checked · all complete. 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- 13sandbox rule tags
- 2spawned processes
- 0network contacts
- 23filesystem & 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
13MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1033· Reads user info
- T1036
- T1055· Process injection
- T1056· Keylogging
- T1069
- T1082· System recon
- T1485
- T1497· Sandbox evasion
- T1518.001· Checks your AV
- T1542.003
- T1553
- T1553.002
Observed activity
Processes started
2Programs the file ran, with their command lines.
executable.exe"C:\Users\<USER>\Desktop\executable.exe"file.exe"C:\Users\user\Desktop\file.exe"
Files
15Files the file created, changed or deleted.
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\e5998c1b-1de2-4a7f-887f-ed0f01ff6ad6 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\f9d3820d-e4e3-4549-ae2a-f68beea06cf8 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\d644a2ef-2816-40ca-b1c1-074c22aa68af
Show all 15 entries for files
- Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\f8323b4c-c892-4d84-adc4-25b1dceb1567 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\265bf998-d67b-4ac1-8b77-87383eb0aecc - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\3a3213b0-620a-4fdf-ab4e-14ff44ed9633 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\7988342e-5e5e-40ec-a11d-d043aacff31b - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6469e95b-3b7c-4b81-b231-e1fbdc7a5902.tmp.WERInternalMetadata.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e15e7494-d6f4-442d-8e56-1494552ae54e.tmp.dmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\acffc3c7-3ddb-47d3-b749-8ec7f4d872a0 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\bc8baf80-8b75-4051-b419-0599773b0f69 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\f0f03dcf-a30b-4f1a-af1f-e58bcd832238
Registry and auto-start
15Settings the file changed, including ways to start again after a restart.
- Set
HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties - Set
HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties - Set
HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput - Set
HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0627&PID_0001 - Set
HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0627&PID_0001\Calibration - Set
HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0627&PID_0001\Calibration\0
Show all 15 entries for registry and auto-start
- Set
HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0627&PID_0001\DeviceInstances - Set
HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0627&PID_0001\Calibration\0\GUID - Set
\REGISTRY\A\{ac5b129d-0f5a-4292-cfb4-eb7849b7b4f7}\Root\InventoryApplicationFile\PermissionsCheckTestKey - Set
\REGISTRY\A\{ac5b129d-0f5a-4292-cfb4-eb7849b7b4f7}\Root\InventoryApplicationFile\file.exe|3bfeaaf1919d30b - Set
\REGISTRY\A\{ac5b129d-0f5a-4292-cfb4-eb7849b7b4f7}\Root\InventoryApplicationFile\file.exe|3bfeaaf1919d30b\ProgramId - Set
\REGISTRY\A\{ac5b129d-0f5a-4292-cfb4-eb7849b7b4f7}\Root\InventoryApplicationFile\file.exe|3bfeaaf1919d30b\FileId - Set
\REGISTRY\A\{ac5b129d-0f5a-4292-cfb4-eb7849b7b4f7}\Root\InventoryApplicationFile\file.exe|3bfeaaf1919d30b\LowerCaseLongPath - Set
\REGISTRY\A\{ac5b129d-0f5a-4292-cfb4-eb7849b7b4f7}\Root\InventoryApplicationFile\file.exe|3bfeaaf1919d30b\Name - Set
\REGISTRY\A\{ac5b129d-0f5a-4292-cfb4-eb7849b7b4f7}\Root\InventoryApplicationFile\file.exe|3bfeaaf1919d30b\BinaryType
Mutexes
8Named locks a program uses so only one copy runs; malware families often reuse them.
Global\OneSettingQueryMutex+compat+encapsulationDirectInput.{89521361-AA8A-11CF-BFC7-444553540000}DirectInput.{5944E682-C92E-11CF-BFC7-444553540000}\Sessions\1\BaseNamedObjects\DirectInput.{89521361-AA8A-11CF-BFC7-444553540000}\Sessions\1\BaseNamedObjects\DirectInput.{5944E682-C92E-11CF-BFC7-444553540000}\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess7112
Show all 8 entries for mutexes
\Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex4012\Sessions\1\BaseNamedObjects\Global\a6fef8a0-35b3-4ea7-8c63-845f45ee2d8e
Sandbox background — not the file
12The analysis machine's own processes and connections, recorded in every run.
- VM process
WerFault.exeC:\Windows\system32\WerFault.exe -u -p 6140 -s 1196 - VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s WdiSystemHost
Show all 12 entries for sandbox background — not the file
- VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time - VM process
lsass.exeC:\Windows\system32\lsass.exe - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalSystemNetworkRestricted -p - VM process
WerFault.exeC:\Windows\System32\WerFault.exe C:\Windows\system32\WerFault.exe -u -p 7112 -s 1132 - VM host
atm.teams.mira.tm.svc.cloud.microsoft - VM host
162.159.36.2
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache. 1 has no saved verdict and was not checked; that is missing coverage, not a finding.
- 4506e81d49d844d83efb…eb5725Not checkedno saved verdict
Chapter 04
Technical details
2 of the 71 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 2
The saved verdict treats these detections as likely false positives.
- APEXMalicious
- Trapminesuspicious.low.ml.score
File fingerprint
- Last analyzed
- Oct 12, 2026, 4:13 PM UTC
- SHA-256
19c1a32076a69a2ef5d8eb6bc507de6d5ffb9427081954dc9bc6980540efbb6d- SHA-1
e7998edd2d0721df4d96c9aca346bd08209c902b- MD5
acde2152cf6249c6810f3a9d4d96da69
About this file
SimpsonsWrestling.exe is a Win32 EXE file of 2.6 MB.
- Type and size
- Win32 EXE · 2.6 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 8, 2026On VirusTotal.
- Submitted by
- 6 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 6.33 of 8
First scanned
Antivirus consensus
2 of 71 engines flagged this file
4 of the 75 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-trust17 engines2flagged
View all 75 engine results
- APEXMalicious: Malicious
- TrapmineMalicious: suspicious.low.ml.score
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- 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
- 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is SimpsonsWrestling.exe safe?
What is SimpsonsWrestling.exe?
How many antivirus engines detected SimpsonsWrestling.exe?
What is the SHA-256 hash of SimpsonsWrestling.exe?
Is it safe to run SimpsonsWrestling.exe?
How up to date is this analysis of SimpsonsWrestling.exe?
Community
Member reviews and reports for this exact file hash.