File scan report
Verdict Safe
Is 6f1835e4-
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
Includes 24 mapped techniques, every process, file, registry and network entry and 7 dropped files.
Show the technical evidenceChapter 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
Includes every engine result (74), 1 matched signature rule and how widely the file has been seen.
Show the technical evidenceChapter 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.