Is 6f1835e4-9bd9-4c61-a73f-ed8d8c1e366e safe?
Safe file assessment
0 of 74 antivirus engines flagged the file.
6ec9209c64a53e7a98…ce0fc384e11b9dRecommended next actions
Before opening or extracting
Open or extract it only when its sender or download source has been independently verified.
If you already opened or extracted 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.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 3 contacted hosts were cross-checked; coverage is incomplete.
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
- 24MITRE ATT&CK techniques
- 15spawned processes
- 4network contacts
- 40filesystem & 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
6f1835e4-9bd9-4c61-a73f-ed8d8c1e366e
6ec9209c64a53e7a9848ccc09a0839fcf7295971e945cf1166ce0fc384e11b9d
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\Trinity/Trinity.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Trinity/vcruntime140.dll",#1
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
41f04f0c-cc38-4a1d-920c-468bdf4f760b
C:\ProgramData\Microsoft\Windows\WER\Temp\41f04f0c-cc38-4a1d-920c-468bdf4f760b
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
8.8.8.8
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
172.64.149.23
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.
- 8.8.8.8
- 172.64.149.23
- http://ocsp.sectigo.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBSdE3gf41WAic8Uh9lF92%2BIJqh5qwQUMuuSmv81lkgvKEBCcCA2kVwXheYCEGIdbQxSAZ47kHkVIIkhHAo%3D
- http://ocsp.sectigo.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBQVD%2BnGf79Hpedv3mhy6uKMVZkPCQQUDyrLIIcouOxvSK4rVKYpqhekzQwCEAajmICyUarJo3PdWocUg94%3D
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\41f04f0c-cc38-4a1d-920c-468bdf4f760b
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\dac17e04-f1fa-491f-abc5-6a6960750c72
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B31.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER9292.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER966C.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B31.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER9292.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess3572
- Global\3a8f8214-07ab-47de-b04a-aead1e7ca9c7
- Local\WERReportingForProcess5188
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\b25db408-8b20-425f-a6d4-9a9e47c20254
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 3e363bf82545f24cce8c…308a5dNever scannednever seen before
- 48f4a239c25354f0e9f8…17ecedNever scannednever seen before
- 359c9c02a9fa3de10ba4…52ab21Never scannednever seen before
- e9b7aecd456f1d228860…b73ec2Never scannednever seen before
- 20139f4c327711baf182…72ed94Never scannednever seen before
- 3271d39d7b4dcd841e8e…efe5e5Never scannednever seen before
- cb71909bf01a3a7a4c73…d46e13Never scannednever seen before
- 9fac69dc609cc6074ecd…fc54f6Never scannednever seen before
- e65d6e5e837df0a2df0d…2d9d6cNever scannednever seen before
- 1b1663859d7ee7ca0fcd…bac119Never 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 / 74engines flagged
- 1sources 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 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: 6f1835e4-9bd9-4c61-a73f-ed8d8c1e366e — 6ec9209c64a53e7a9848ccc09a0839fcf7295971e945cf1166ce0fc384e11b9d
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\Trinity/Trinity.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Trinity/vcruntime140.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 41f04f0c-cc38-4a1d-920c-468bdf4f760b — C:\ProgramData\Microsoft\Windows\WER\Temp\41f04f0c-cc38-4a1d-920c-468bdf4f760b
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 8.8.8.8 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 172.64.149.23 — 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.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
Evidence"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Trinity/vcruntime140.dll",#1The 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.
Evidence8.8.8.8 · 172.64.149.23
0 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- 6f1835e4-9bd9-4c61-a73f-ed8d8c1e366e
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 44.7 MB
- Last analyzed
- Jul 11, 2026, 4:28 AM UTC
6ec9209c64a53e7a9848ccc09a0839fcf7295971e945cf1166ce0fc384e11b9dSafety & 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
Open or extract it only when its sender or download source has been independently verified.
- 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 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.