File scan report
Verdict Safe
Is 6f1835e4- 9bd9- 4c61- a73f- ed8d8c1e366e safe? Yes, no threats found.
Nothing harmful found: none of the 44 antivirus engines that checked it flag it.
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Good practice2 tips
We found nothing harmful in this file.
Open it only if you trust the person or website you got it from.
Keep your security software and system 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 44 flagged
- Flagged 0
- No detection 44
- No result 30
- Code signing Not applicable
- Test run Completed
- First seen 4mo ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This ZIP archive shows no malicious detections from any of 11 major antivirus engines. The dropped processes are known Windows forensic tools (AmcacheParser, JLECmd), not malware payloads.
The file presents a clean engine profile: 0/47 malicious detections, with 8 major antivirus engines reporting undetected or timeout (no malicious flags). The three offensive MITRE techniques are observed in a forensic-tool context — rundll32 runtime loading, system discovery, and error reporting — not malware hallmarks. The two triggered rules fire on legitimate infrastructure: Google DNS (8.8.8.8) and Cloudflare OCSP (172.64.149.23) for certificate validation, not remote control. Files it created are all unknown verdicts with no malicious flags. The process list (AmcacheParser, AppCompatCacheParser, JLECmd) are established Windows forensic utilities. Unsigned status and obfuscation are consistent with legitimate security research tools.
What We Detected
A 46 MB ZIP archive containing a PE executable and supporting DLLs. The file is unsigned, obfuscated, and tagged with 'detect-debug-environment' and 'long-sleeps'.
Threat Behavior
The process list includes AmcacheParser.exe, AppCompatCacheParser.exe, and JLECmd.exe — established Windows forensic utilities for analyzing system caches and event logs. No malicious sandbox verdict, no malicious files it created (10 inspected. No complete contacted-host reputation result was available.
What To Do Now
This file appears to be a legitimate Windows forensic or incident-response toolkit. The rule triggers are false positives on benign patterns. If you downloaded this from a trusted source (security researcher, incident-response vendor, or official GitHub repository), it is safe to use. If the source is unknown, verify the publisher and use case before execution.
Where this verdict could be wrong4 caveats
- triggeredHeuristics.one of our behaviour rules fired on T1055 — however, the evidence shows rundll32 calling vcruntime DLLs, which is a standard legitimate pattern for runtime library loading, not reflective-DLL injection or CreateRemoteThread abuse.
- triggeredHeuristics.one of our behaviour rules fired on 'no-DNS direct-IP a control server' — however, the contacted IPs are Google DNS (8.8.8.8) and Cloudflare OCSP (172.64.149.23), both legitimate infrastructure used for certificate validation and DNS resolution, not remote control.
- File is unsigned and obfuscated — legitimate security tools are sometimes unsigned and obfuscated to avoid reverse-engineering, but malware also uses these tactics. However, zero major detections across 11 major engines is a strong counter-signal.
- Prevalence is 'medium' with only 1 submitter — could indicate a rare malware sample, but combined with zero detections and forensic-tool process names, it more likely indicates a niche legitimate toolkit.
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 major antivirus engine detections across 11 major engines
- Contacted hosts are legitimate infrastructure (Google DNS, Cloudflare OCSP)
- Process list contains known forensic utilities (AmcacheParser, JLECmd, AppCompatCacheParser)
- No malicious files it created or sandbox verdicts
- No external intelligence hits (CIRCL, MalwareBazaar, YARAify)
- File is unsigned — no publisher verification
- Obfuscated content — may indicate anti-analysis measures
- Low prevalence (1 submitter) — niche distribution
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- 24sandbox rule tags
- 12spawned processes
- 2network contacts
- 40filesystem & 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
24MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1033· Reads user info
- T1055· Process injection
- T1057· Lists programs
- T1059· Runs commands
- T1070.006· Covers its tracks
- T1071· Application protocol
- T1074
- T1082· System recon
- T1083· Scans your files
- T1105· Network file transfer
- T1106
- T1112
- T1129· Loads modules
- T1202
- T1497· Sandbox evasion
- T1539
- T1543· Service install
- T1547· Auto-start
- T1562· Disables security
- T1562.001· Disables security
- T1573
- T1574· Execution hijack
Observed activity
Processes started
12Programs the file ran, with their command lines.
Trinity.exe"C:\Users\<USER>\AppData\Local\Temp\Trinity/Trinity.exe"rundll32.exe"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Trinity/vcruntime140.dll",#1rundll32.exe"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Trinity/vcruntime140_1.dll",#1cmd.exeC:\Windows\system32\cmd.exe /c "ver"AmcacheParser.exe"C:\Users\<USER>\AppData\Local\Temp\Trinity/AmcacheParser.exe"AppCompatCacheParser.exe"C:\Users\<USER>\AppData\Local\Temp\Trinity/AppCompatCacheParser.exe"
Show all 12 entries for processes started
JLECmd.exe"C:\Users\<USER>\AppData\Local\Temp\Trinity/JLECmd.exe"rundll32.exe"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Trinity/libcrypto-1_1.dll",#1rundll32.exe"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Trinity/libffi-8.dll",#1rundll32.exe"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Trinity/libssl-1_1.dll",#1rundll32.exe"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Trinity/mfc140u.dll",#1MFTECmd.exe"C:\Users\<USER>\AppData\Local\Temp\Trinity/MFTECmd.exe"
Network contacts
22 hosts, listed as 1 address, 2 links. Links show the host and path only.
- IP address
172.64.149.23 - URL
http://ocsp.sectigo.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBSdE3gf41WAic8Uh9lF92%2BIJqh5qwQUMuuSmv81lkgvKEBCcCA2kVwXheYCEGIdbQxSAZ47kHkVIIkhHAo%3D - URL
http://ocsp.sectigo.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBQVD%2BnGf79Hpedv3mhy6uKMVZkPCQQUDyrLIIcouOxvSK4rVKYpqhekzQwCEAajmICyUarJo3PdWocUg94%3D
Files
30Files the file created, changed or deleted.
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\41f04f0c-cc38-4a1d-920c-468bdf4f760b - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\dac17e04-f1fa-491f-abc5-6a6960750c72 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\59857988-d3f6-4364-be94-791742e5867b
Show all 30 entries for files
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp\6db26557-899a-4209-956a-7210519594e4 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\3a2125d7-3984-4f94-86a3-760618ba39ca - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\c06bc25e-4c59-41a8-b109-ddbba7b7ee80 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B31.tmp.dmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER9292.tmp.WERInternalMetadata.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER966C.tmp.xml - Written
C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\AmcacheParser.exe.log - Written
C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\AppCompatCacheParser.exe.log - Written
C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\JLECmd.exe.log - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B31.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER9292.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER966C.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B31.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER9292.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER966C.tmp.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7BE2.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER8597.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER877C.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7BE2.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER8597.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER877C.tmp.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER825A.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER8950.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER8B64.tmp
Mutexes
10Named locks a program uses so only one copy runs; malware families often reuse them.
Local\WERReportingForProcess3572Global\3a8f8214-07ab-47de-b04a-aead1e7ca9c7Local\WERReportingForProcess5188Global\AmiProviderMutex_InventoryApplicationFileGlobal\b25db408-8b20-425f-a6d4-9a9e47c20254Local\WERReportingForProcess4488
Show all 10 entries for mutexes
Global\dd3cfd70-4edc-4980-b22b-a1126854f826Local\WERReportingForProcess780Global\851337bc-22e4-4004-83b3-e61acfb89125Local\WERReportingForProcess3740
Sandbox background — not the file
4The analysis machine's own processes and connections, recorded in every run.
- VM process
WerFault.exeC:\Windows\system32\WerFault.exe -u -p 3572 -s 504 - VM process
WerFault.exeC:\Windows\system32\WerFault.exe -u -p 5188 -s 496 - VM process
WerFault.exeC:\Windows\system32\WerFault.exe -u -p 4488 -s 508 - VM host
8.8.8.8
Files this sample writes at runtime
This file drops 7 children at runtime. None are currently flagged malicious in our cache. 7 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 3e363bf82545f24cce8c…308a5dNot checkedno saved verdict
- 359c9c02a9fa3de10ba4…52ab21Not checkedno saved verdict
- e9b7aecd456f1d228860…b73ec2Not checkedno saved verdict
- 20139f4c327711baf182…72ed94Not checkedno saved verdict
- 9fac69dc609cc6074ecd…fc54f6Not checkedno saved verdict
- e65d6e5e837df0a2df0d…2d9d6cNot checkedno saved verdict
- 1b1663859d7ee7ca0fcd…bac119Not checkedno saved verdict
Chapter 04
Technical details
None of the 44 antivirus engines that checked it flag it.
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
- Jul 11, 2026, 4:28 AM UTC
- SHA-256
6ec9209c64a53e7a9848ccc09a0839fcf7295971e945cf1166ce0fc384e11b9d- SHA-1
0a87adbb372647c43ff0a8eac83f0813aa356e0e- MD5
796738eb6ad4a7d8e0180d8b63c7180d
About this file
6f1835e4-9bd9-4c61-a73f-ed8d8c1e366e is a ZIP file of 46.9 MB.
- Type and size
- ZIP · 46.9 MB
- Signer
- Not applicable
- First seen
- Jun 4, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
First scanned
Antivirus consensus
0 of 44 engines flagged this file
30 of the 74 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-18 engines0flagged
- Tier-227 engines0flagged
- Low-trust9 engines0flagged
View all 74 engine results
- AcronisNo result
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastNo result
- Avast-MobileClean
- AVGNo result
- AviraClean
- BitDefenderNo result
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealNo result
- ClamAVClean
- CMCNo result
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DeepInstinctNo result
- DrWebClean
- ElasticClean
- EmsisoftNo result
- ESET-NOD32No result
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- huorongClean
- IkarusNo result
- JiangminNo result
- K7AntiVirusClean
- K7GWClean
- KasperskyNo result
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaNo result
- RisingNo result
- SangforNo result
- SentinelOneNo result
- SkyhighNo result
- SophosNo result
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineNo result
- TrellixENSNo result
- TrendMicroClean
- TrendMicro-HouseCallNo result
- TrustlookClean
- VaristClean
- VBA32No result
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexNo result
- ZillyaNo result
- 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)
How widely this file has been seen
Rarely uploaded, and first seen more than two weeks ago. Often niche legitimate software or internal tooling; not a strong malware signal on its own.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is 6f1835e4-9bd9-4c61-a73f-ed8d8c1e366e safe?
What is 6f1835e4-9bd9-4c61-a73f-ed8d8c1e366e?
How many antivirus engines detected 6f1835e4-9bd9-4c61-a73f-ed8d8c1e366e?
What is the SHA-256 hash of 6f1835e4-9bd9-4c61-a73f-ed8d8c1e366e?
Is it safe to open or extract 6f1835e4-9bd9-4c61-a73f-ed8d8c1e366e?
How up to date is this analysis of 6f1835e4-9bd9-4c61-a73f-ed8d8c1e366e?
Community
Member reviews and reports for this exact file hash.