File scan report
Verdict Safe
Is Blox
No antivirus engine flagged this exact release archive, and its clean sandbox result plus established GitHub release identity outweigh the unconfirmed behavior mappings.
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.
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 67 flagged
- Flagged 0
- No detection 67
- No result 8
- Code signing Not applicable
- Test run Completed
- First seen 1mo ago
Chapter 02
Why we think so
2 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 67 antivirus engines that checked it flagged the archive, including all 17 major antivirus engines that returned results.
The archive drew no malicious or suspicious detection from 75 engines, with all 17 reporting major antivirus engines silent. Its SHA-256 exactly matches the v5.4.1 asset published by an established GitHub repository, providing strong provenance evidence. One completed sandbox run returned a clean result, and the complete reputation check of its five observed hosts found no known hostile endpoint. The test run nevertheless mapped possible process injection and impairment of defenses, but it identified no injected target or method and found no persistence. Eight extracted files lack saved individual verdicts, so that file it created coverage remains incomplete despite the absence of a known malicious child. Overall, the provenance and broad detection silence outweigh those uncorroborated behavioral mappings.
What We Detected
None of the 67 antivirus engines that checked it flagged the ZIP archive, including the 17 major antivirus engines that returned results. The file is byte-identical to the BloxDump v5.4.1 asset published by the established EmK530/BloxDump repository.
Threat Behavior
One completed sandbox run returned a clean result. It mapped possible process injection and impairment of defenses, but recorded no injected target, injection method, persistence, malicious child, or known hostile host. The observed GitHub downloads are consistent with fetching a dependency, while two separately identified background contacts were excluded from sample activity.
What To Do Now
Obtain the archive from the project's official release page and verify its SHA-256 as 9aa6e93f349c7ff1db3045360b4c9bcad41be2e1eeaeb37dc490d653ac73f0ad. Keep security software enabled, particularly because the archive contains executables and eight extracted files do not have saved individual verdicts.
Where this verdict could be wrong2 caveats
- Runtime mapping included possible process injection and impairment of defenses, although no injected process, injection method, persistence, or hostile endpoint was identified.
- Eight extracted files have no saved individual verdicts, so their contents are not independently cleared by file it created 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.
- Byte-identical to BloxDump.v5.4.1.zip in EmK530/BloxDump release v5.4.1 (published Sep 12, 2026).
- No engine among the 75-engine network flagged the archive.
- All 17 major antivirus engines that returned results reported no detection.
- The completed sandbox run returned a clean result and identified no persistence.
- The reputation check covered all five distinct observed hosts and found no known malicious or suspicious matches.
- The test run mapped possible process injection and impairment of defenses, although it did not identify a target or concrete injection method.
- The archive contains executable content, and eight extracted files lack saved individual verdicts.
7 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- 11sandbox rule tags
- 9spawned processes
- 4network contacts
- 31filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
11MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1033· Reads user info
- T1055· Process injection
- T1057· Lists programs
- T1059· Runs commands
- T1071· Application protocol
- T1082· System recon
- T1202
- T1497· Sandbox evasion
- T1562.001· Disables security
- T1573
- T1574· Execution hijack
Observed activity
Processes started
9Programs the file ran, with their command lines.
BloxDump.exe"C:\Users\<USER>\AppData\Local\Temp\BloxDump.exe"cmd.exe"cmd.exe" /C clsrundll32.exe"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\draco_tiny_dec.dll",#1rundll32.exe"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\ktx.dll",#1rundll32.exe"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\sni.dll",#1rundll32.exe"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\SQLite.Interop.dll",#1
Show all 9 entries for processes started
cmd.execmd.exe /C clsunarchiver.exeC:\Windows\SysWOW64\unarchiver.exe "C:\Windows\SysWow64\unarchiver.exe" "C:\Users\user\Desktop\BloxDump.v5.4.1.zip"7za.exeC:\Windows\SysWOW64\7za.exe "C:\Windows\System32\7za.exe" x -pinfected -y -o"C:\Users\user\AppData\Local\Temp\tw201jgp.jgh" "C:\Users\user\Desktop\BloxDump.v5.4.1.zip"
Network contacts
44 hosts, listed as 2 domains, 2 addresses, 2 links. Links show the host and path only.
- Domain
github.com - Domain
release-assets.githubusercontent.com - IP address
140.82.114.3 - IP address
185.199.109.133 - URL
https://github.com/EmK530/BloxDump/releases/download/dependencies/ffmpeg.exe - URL
https://release-assets.githubusercontent.com/github-production-release-asset/711620803/82e4c493-b1df-4756-82c8-24adc456a4ac
Files
27Files the file created, changed or deleted.
- Written
C:\Users\<USER>\Desktop\config.json - Written
C:\Users\<USER>\Desktop\ffmpeg.exe - Written
C:\ProgramData\Microsoft\Windows\WER\Temp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\2549c14b-f9c4-4fe2-8c0f-441ff384cf08 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\4ae0589a-1b1f-4d69-9e21-0491c0db3416
Show all 27 entries for files
- Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\a5064716-2515-40ce-99a0-f6077f5aadbd - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\ec7a936d-60f5-46ce-8c94-553e6f7d18db - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\5db4b39d-7d5b-4e22-82b3-374d82faa4a1 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\085686d7-f90c-4b78-b033-0f81e2112f42 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AA.tmp.dmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WERA8B.tmp.WERInternalMetadata.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WERFFB.tmp.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\ed1829bf-fb7f-4376-a86a-10dbad448158 - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AA.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERA8B.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERFFB.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AA.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERA8B.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERFFB.tmp.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C7C.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2508.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E2.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C7C.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2508.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E2.tmp.xml
Mutexes
4Named locks a program uses so only one copy runs; malware families often reuse them.
Local\WERReportingForProcess2216Global\b7ea1ae9-d24f-480c-995f-c79b37876d39Local\WERReportingForProcess7128Global\10fddf70-7cc7-4011-befb-efe45c01f4c0
Sandbox background — not the file
5The analysis machine's own processes and connections, recorded in every run.
- VM process
WerFault.exeC:\Windows\system32\WerFault.exe -u -p 2216 -s 572 - VM process
WerFault.exeC:\Windows\system32\WerFault.exe -u -p 7128 -s 588 - VM process
conhost.exeC:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1 - VM host
assets.msn.com - VM host
162.159.36.2
Files this sample writes at runtime
This file drops 8 children at runtime. None are currently flagged malicious in our cache. 8 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 6e67e7aff61982eaeea1…502016Not checkedno saved verdict
- 65f0699eaeaca97b8d56…62887cNot checkedno saved verdict
- 22068014a3e7783e12a8…5f49c1Not checkedno saved verdict
- 68705c4ef9ab818f2956…9b47d6Not checkedno saved verdict
- 1111916dc329a13bd627…360c37Not checkedno saved verdict
- 19efc7b21247efc3962c…8162c0Not checkedno saved verdict
- b90225987bdd042cca09…522997Not checkedno saved verdict
- 01a2abcd79e2c969e528…58cd7bNot checkedno saved verdict
Chapter 04
Technical details
None of the 67 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
7 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 15, 2026, 4:04 AM UTC
- SHA-256
9aa6e93f349c7ff1db3045360b4c9bcad41be2e1eeaeb37dc490d653ac73f0ad- SHA-1
44a3ce877dc4234fd2811fa1efef0d865806acad- MD5
f4f3f20cef5066a2739be0f254886dbf
About this file
BloxDump.v5.4.1.zip is a ZIP file of 11.9 MB.
- Type and size
- ZIP · 11.9 MB
- Signer
- Not applicable
- First seen
- Sep 13, 2026On VirusTotal.
- Submitted by
- 31 distinct sources
First scanned
Antivirus consensus
0 of 67 engines flagged this file
8 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-trust13 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastClean
- Avast-MobileClean
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- 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
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineNo result
- 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)
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 BloxDump.v5.4.1.zip safe?
What is BloxDump.v5.4.1.zip?
How many antivirus engines detected BloxDump.v5.4.1.zip?
What is the SHA-256 hash of BloxDump.v5.4.1.zip?
Is it safe to open or extract BloxDump.v5.4.1.zip?
How up to date is this analysis of BloxDump.v5.4.1.zip?
Community
Member reviews and reports for this exact file hash.