File scan report
Verdict Safe
Is Bedrock
No antivirus engine detected a threat, and evidence from the test run showed no corroborated high-risk activity, malicious host, or malicious dropped file.
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.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Antivirus results
0 of 69 flagged
- Flagged 0
- No detection 69
- No result 6
- Code signing Unsigned
- Test run Completed
- First seen 10d ago
Chapter 02
Why we think so
3 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 69 antivirus engines that checked it flagged the executable, including the major engines represented in the results. Evidence from the test run contained only unsupported technique mappings, while the complete host-reputation check found no malicious or suspicious host; however, the file is unsigned and lacks direct static inspection.
None of the 69 antivirus engines that checked it flagged the file, and 18 major engines reported no detection. The sandbox runs did not produce a malicious verdict, named injection target, persistence indicator, or corroborated high-risk technique. The observed network contacts were fully covered by the saved reputation check, which found no malicious or suspicious host. The executable is also not packed, and no malicious file it created or malware-specific community rule was identified. Confidence is moderated because it is unsigned, has modest prevalence, and the bytes were not available for our static analysis.
What We Detected
None of the 69 antivirus engines that checked it flagged the executable, including 18 major engines that reported no detection. No malware family was identified, no packing was found, and the external reference checks produced no malware-specific match.
Threat Behavior
The sandbox runs recorded activity commonly seen in ordinary applications. The complete reputation check covering the two distinct observed hosts found neither a malicious nor suspicious host, and no malicious dropped file was identified.
What To Do Now
The available evidence supports normal use if the file came from the source you intended. Because the executable is unsigned and our static analysis was unavailable, keep security software enabled and obtain it from the publisher's established distribution channel.
Where this verdict could be wrong3 caveats
- The executable is unsigned and was first seen on Oct 27, 2026, with only 18 distinct submitters, so its publisher and long-term history are not established.
- No completed static analysis of the uploaded bytes is available, limiting direct inspection of the executable's contents.
- A prior file with the same import-table fingerprint received a malicious decision, although that weak match had no matching signer and can occur across unrelated software.
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 69 antivirus engines that checked it flagged the file, and 18 major engines reported no detection.
- The sandbox runs produced no malicious verdict and named no process targeted for injection.
- The complete reputation check covering the two distinct observed hosts found no malicious or suspicious host.
- No malicious dropped file, packer, or malware-specific community rule was identified.
- The executable has no verified publisher signature.
- It was first seen on Oct 27, 2026, and has been submitted by 18 distinct sources, providing only a modest history.
- Direct static inspection of the uploaded bytes was not available.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 5 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 5isolated sandbox runs
- 21sandbox rule tags
- 2spawned processes
- 2network contacts
- 32filesystem & mutex artifacts
What this file did when executed
This file was detonated in 5 sandboxes and its runtime behaviour was observed.
Techniques observed in the sandbox
21MITRE 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
- T1036
- T1047
- T1055· Process injection
- T1059· Runs commands
- T1069
- T1071· Application protocol
- T1074
- T1082· System recon
- T1105· Network file transfer
- T1129· Loads modules
- T1485
- T1486· File encryption
- T1497· Sandbox evasion
- T1553
- T1553.002
- T1562· Disables security
- T1562.001· Disables security
- T1574· Execution hijack
Observed activity
Processes started
2Programs the file ran, with their command lines.
BedrockToolchest.exe"C:\Users\<USER>\Desktop\BedrockToolchest.exe"BedrockToolchest.exe"C:\Users\user\Desktop\BedrockToolchest.exe"
Network contacts
22 hosts, listed as 1 domain, 1 address, 1 link. Links show the host and path only.
- Domain
bedrocktoolchest.com - IP address
172.67.191.124 - URL
https://bedrocktoolchest.com/api/version-check.php
Files
30Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\.net\BedrockToolchest\abc\av_libglesv2.dll - Written
C:\Users\<USER>\AppData\Local\Temp\.net\BedrockToolchest\abc\libHarfBuzzSharp.dll - Written
C:\Users\<USER>\AppData\Local\Temp\.net\BedrockToolchest\abc\libSkiaSharp.dll - Written
C:\Users\<USER>\AppData\Local\Temp\.net\BedrockToolchest\UODJltCNB7_r - Written
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\ar.json.0ecd33afce364d14a8840140d7e682b9.tmp - Written
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\ar.json
Show all 30 entries for files
- Written
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\de.json.101bafa7481b48d2ac7568fec723ac09.tmp - Written
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\de.json - Written
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\en.json.b5366f0f32264481b56ce46e24c303e0.tmp - Written
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\en.json - Written
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\es.json.3ecc4602eaba4684a7e0b33f2e26123e.tmp - Written
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\es.json - Written
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\fr.json.76b75e7ee57048e5a1a204c102679cf0.tmp - Written
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\fr.json - Written
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\hi.json.2d1b8182283c43eda2f4d3f45a7ec095.tmp - Deleted
C:\Users\<USER>\AppData\Local\Temp\.net\BedrockToolchest\abc - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\ar.json.0ecd33afce364d14a8840140d7e682b9.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\de.json.101bafa7481b48d2ac7568fec723ac09.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\en.json.b5366f0f32264481b56ce46e24c303e0.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\es.json.3ecc4602eaba4684a7e0b33f2e26123e.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\fr.json.76b75e7ee57048e5a1a204c102679cf0.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\hi.json.2d1b8182283c43eda2f4d3f45a7ec095.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\id.json.1b1503f96c8841e68325db53a3ef79a3.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\it.json.07fda9ab298d4a0088f280084bf9e42f.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\ja.json.4f5af29ea9254790b15d1d074fec7dc9.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\ko.json.ae3db6f0c09a4dbaa3a507997548244f.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\nl.json.bc9287e3615f43f480d7af5f4c4b0021.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\pl.json.4ad2f968a4804c70941ecb0be569b988.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\pt_BR.json.ab366dc1e19647648d5e85a4399a17af.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\BedrockToolchest\v3\languages\ru.json.5a7fbbcecaa14825a80f7d8026aeef0b.tmp
Registry and auto-start
2Settings the file changed, including ways to start again after a restart.
- Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\SessionInfo\1\ApplicationViewManagement\W32:0000000000030038\VirtualDesktop - Set
HKEY_USERS\S-1-5-21-4270068108-2931534202-3907561125-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.exe\OpenWithProgids\exefile
Mutexes
2Named locks a program uses so only one copy runs; malware families often reuse them.
Local\SessionImmersiveColorMutexGlobal\OneSettingQueryMutex+compat+encapsulation
Sandbox background — not the file
9The analysis machine's own processes and connections, recorded in every run.
- VM process
Explorer.EXEC:\Windows\Explorer.EXE - VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s WdiSystemHost
Show all 9 entries for sandbox background — not the file
- VM process
lsass.exeC:\Windows\system32\lsass.exe - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalSystemNetworkRestricted -p - VM host
162.159.36.2
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 53191a77fe783cd757ca…0b73e3Not checkedno saved verdict
- 145ade963eba427027d5…da246fNot checkedno saved verdict
- 7dec3ba900ab353491e6…dbbe1cNot checkedno saved verdict
- 8ea54b6b4a2e90a7a0d8…474718Not checkedno saved verdict
- 7ee3f06ae186300e1633…62e237Not checkedno saved verdict
- 07523c3d9cab7a183f2f…a9be52Not checkedno saved verdict
- 75438b38a9e74a7bbd16…6dcf7aNot checkedno saved verdict
- 57896f1c78aca332c53a…bd8ef3Not checkedno saved verdict
- 40aeebd53dd82f06b65d…618e75Not checkedno saved verdict
- 67ee2fb79f72b8c0be09…2c0911Not checkedno saved verdict
Chapter 04
Technical details
None of the 69 antivirus engines that checked it flag it; no publisher signature.
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
- Nov 6, 2026, 2:41 PM UTC
- SHA-256
c9110025450915feabcbabdbc40e80df4ee9ee8c2cda18105d662bc29ee10685- SHA-1
2333fe135bafc29bf479f3acad3c08fed4f3df42- MD5
b5bda42663282aa1ebcd5a66abb7c2d2
About this file
BedrockToolchest.dll is a Win32 EXE file of 66.8 MB.
- Claims to be
- BedrockToolchest (Bedrock Toolchest)From the file's own version information, written by whoever built it.
- Original name
- BedrockToolchest.dllMatches the shared file name.
- Type and size
- Win32 EXE · 66.8 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 27, 2026On VirusTotal.
- Submitted by
- 18 distinct sources
- Packer
- None detected
- Entropy
- 6.33 of 8
First scanned
Antivirus consensus
0 of 69 engines flagged this file
6 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-234 engines0flagged
- Low-trust17 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXNo result
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticNo result
- 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
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- 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)
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
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 BedrockToolchest.dll safe?
What is BedrockToolchest.dll?
How many antivirus engines detected BedrockToolchest.dll?
What is the SHA-256 hash of BedrockToolchest.dll?
Is it safe to run BedrockToolchest.dll?
How up to date is this analysis of BedrockToolchest.dll?
Community
Member reviews and reports for this exact file hash.