File scan report
Verdict Safe
Is SDI_
No antivirus engine flagged this archive, and its sandbox run found no confirmed malware, though several offensive technique mappings justify ordinary source verification.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Use the archive only if it came from the expected official source, and verify its hash. Keep security protection enabled and rescan the extracted executables individually before launch.
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.
Antivirus results
0 of 60 flagged
- Flagged 0
- No detection 60
- No result 15
- Code signing Not applicable
- Test run Completed
- First seen 6mo 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
None of the 60 antivirus engines that checked it flagged the archive, including all 17 major antivirus engines, and the completed sandbox run returned clean. The mapped T1055, T1485, and techniques are cautionary, but no injection target, malicious host, persistence, or confirmed malicious child was identified.
The strongest evidence is the complete absence of detections among 75 engines, with 17 major antivirus engines also reporting no detection. One completed sandbox run returned clean, and the observed contacts were fully cross-checked without a known malicious or suspicious host match. The runtime nevertheless mapped T1055, T1485, and T1562.001, so its behavior is not entirely routine; notably, no injected process target was recorded. Ten files were extracted, but each lacks a saved individual verdict, making their contents an area of incomplete coverage rather than evidence of harm. No MalwareBazaar family or malware-specific YARA rule corroborated the unvoted community allegations.
What We Detected
None of the 60 antivirus engines that checked it flagged the 7-Zip archive, and all 17 major antivirus engines that reported a result found no detection. No named malware family was identified, and neither MalwareBazaar nor malware-specific YARA rules supplied corroboration.
Threat Behavior
One completed sandbox run returned clean. It mapped T1055, T1485, and T1562.001, which can represent process injection, data destruction, and security-control impairment; however, no injected target process, persistence indicator, or malicious sandbox conclusion was recorded. All five distinct non-background contacted hosts were checked without a known malicious or suspicious match. Ten extracted files lack saved individual verdicts, so their child-level status remains unverified.
What To Do Now
Obtain the archive from the project's official distribution channel and verify its hash before extracting it. Keep security software enabled, and inspect or rescan the extracted executables individually before running them, especially if the download source is uncertain.
Where this verdict could be wrong3 caveats
- The sandbox mapped process injection, data destruction, and security-control impairment techniques, although it returned a clean result and identified no injected process.
- All ten extracted files lack saved individual verdicts, so the contents do not have complete child-level coverage.
- Two unvoted community annotations allege serious threats, but they provide no corroborated family identification and conflict with the engine and sandbox results.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 60 antivirus engines that checked it flagged the archive.
- All 17 reporting major antivirus engines found no detection.
- The completed sandbox run returned clean and recorded no persistence.
- All observed non-background hosts were checked with no known malicious or suspicious matches.
- No recognized malware family or malware-specific research rule matched the sample.
- The sandbox mapped process injection, data destruction, and security-control impairment techniques.
- Ten extracted files do not have saved individual verdicts.
- The archive executes batch files and a bundled executable from a temporary directory.
- Two unvoted community annotations allege threats without corroborated family evidence.
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- 10sandbox rule tags
- 9spawned processes
- 5network contacts
- 23filesystem & mutex artifacts
Includes the sandbox verdicts, 10 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 60 antivirus engines that checked it flag it.
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.
File fingerprint
- Last analyzed
- Oct 13, 2026, 2:37 PM UTC
- SHA-256
94014426534e870a76f57d28b30e6d972f217cf384837ac110ed778a262439ce- SHA-1
281b58dc7a70f88169516ffad845b1e22dcfbec5- MD5
245b4ae46a9922ae99b428aa9b0b5813
About this file
SDI_R2601.7z is a 7ZIP file of 6.3 MB.
- Type and size
- 7ZIP · 6.3 MB
- Signer
- Not applicable
- First seen
- Apr 19, 2026On VirusTotal.
- Submitted by
- 2,164 distinct sources
First scanned
Includes every engine result (75), 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 SDI_R2601.7z safe?
What is SDI_R2601.7z?
How many antivirus engines detected SDI_R2601.7z?
What is the SHA-256 hash of SDI_R2601.7z?
Is it safe to open or extract SDI_R2601.7z?
How up to date is this analysis of SDI_R2601.7z?
Community
Member reviews and reports for this exact file hash.