File scan report
Verdict Malicious
Is capstone. dll safe? No, we rate this exact file malicious.
Four community detection rules tied to known malware families matched this unsigned 64-bit DLL, while only one engine assigned a malicious score and three isolated runs showed no…
Read the whole reasonShow less
Moderate evidence · Few antivirus engines flag it; other checks support the rating.
If you already used it, follow the steps below.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't used it
Don't use this component. Let your antivirus remove this component, then repair or reinstall the program it belongs to from its official website. Don't delete or replace the file by hand.
If you already used it
Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.
If you typed passwords on the device after running it, change them from another device you trust.
If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.
If you already ran it, do these in order.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Antivirus results
1 of 70 flagged
- Flagged 1
- No detection 69
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 5mo ago
Chapter 02
Why we think so
5 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This unsigned DLL matched four community detection rules that reference known malware families and their code patterns, alongside a malicious score from a single engine. Against that, eighteen of the most trusted engines in our network were silent and three isolated execution runs produced no injection, persistence or network callbacks. The split between static rule matches and quiet runtime leaves real doubt about intent, so treat the module as untrusted unless you can confirm where it came from.
The strongest signal here is static: four community detection rules that name malware families and their code patterns all matched this binary. Nothing in the file offsets that weight — it carries no digital signature and no publisher history, and only fourteen distinct sources have ever submitted it, so there is no distribution record suggesting a mainstream, well-known build. The antivirus results point the other way: a single engine returned a generic malicious score with no family name, while eighteen of the highest-confidence engines and the bulk of the rest reported nothing, which on its own would look like a false positive. Three isolated execution runs also came back clean, with no process injection, no persistence and no sample-initiated network traffic; the one contacted address is background traffic of the analysis machine. The structure of the module gives a plausible innocent explanation — the entry points and export names resemble a general disassembly library, and such libraries are frequently embedded in tools and malware alike, which can drag their strings into family-specific rules. Because none of the mitigating factors the evidence would need is present, the rule matches cannot be dismissed, but neither can they be treated as confirmed behaviour.
What We Detected
This is a large 64-bit Windows DLL of roughly 7.5 MB, first seen on May 28, 2026 and submitted by fourteen distinct sources since. It carries no digital signature, so nothing verifies who built or published it. One engine returned a malicious score without naming any family, while eighteen of the highest-confidence engines in our network and most of the others found nothing.
The decisive static lead is a set of four community detection rules that reference known malware families and their code signatures; these matched the file's code and string data. The binary itself is not packed or obfuscated — overall entropy is low at 3.01 and the code sections look like ordinary compiled output — so there is no compression layer hiding the content from those rules.
Threat Behavior
The module was executed in three isolated environments and none of them recorded hostile activity: no injection into other processes, no autostart entries, no dropped files with a malicious verdict, no remote control domains and no offensive high-risk techniques. The only network address recorded was traced to the analysis machine's own background traffic, not to the sample.
Behavioural tags attached to the file include debugger-environment detection, BIOS inspection and WMI queries. Those are common in instrumentation and analysis tooling as well as in code that tries to recognise when it is being examined, so they add context rather than proof. The exported entry points and the way the module was loaded resemble a general-purpose disassembly engine, which is one plausible reason family-specific rules written for malware that bundles such engines would match the engine binary itself.
What To Do Now
Do not run this DLL or load it through rundll32 unless you can confirm exactly where it came from and why you have it. If you were expecting the open-source disassembly library, obtain it from the project's own release page rather than from an unknown copy, and compare the file hash. Keep your antivirus and other protections switched on — several engines are silent on this build, so security software may not alert on it — and submit the file to your security team if it arrived as an unexpected attachment or download.
Where this verdict could be wrong4 caveats
- All three isolated execution runs came back clean: no process injection, no persistence, no file drops and no remote control traffic were recorded.
- Community detection rules often match code and strings shared with legitimate libraries; several families that carry a disassembly engine inside them would trip such rules against the engine binary itself.
- The exported entry points and the layout of this module resemble a widely used open-source disassembly library, which would make the family-rule matches collateral rather than evidence of malicious code.
- Eighteen of the most trusted antivirus engines in our network and the other sixty-odd reporting engines produced nothing at all.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Eighteen of the most trusted engines in our network, and the majority of all reporting engines, found nothing.
- Three isolated execution runs produced no process injection, no persistence, no files it created and no sample-initiated network traffic.
- The file is not packed or obfuscated; code sections have ordinary entropy and structure.
- No listing in public malware sample databases and no confirmed malicious file dropped by it.
- Four community detection rules naming known malware families and their code patterns matched this module.
- The file is unsigned, so there is no verified publisher identity behind it.
- Runtime characteristics recorded during execution include debugger-environment detection, BIOS inspection and WMI queries — behaviour that appears in tooling and in code that tries to recognise analysis environments.
- Only fourteen distinct sources have ever submitted this build, so there is no wide distribution record supporting it.
- One engine returned a high malicious score with no family detail, indicating its own model judged the code dangerous.
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in 3 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 3isolated sandbox runs
- 12sandbox rule tags
- 15spawned processes
- 0network contacts
- 25filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Checked which security software was installed on the test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Threat context
How trojans work
A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
capstone.dll
76958e18380023a68fd1714fa2e01c594cc6db1955a07ad6937b66e66dc5d6c3
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
rundll32.exe
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\readme.dll",#1
Test run - Evidence 3 of 5: ProcessSeen in the test run
loaddll64.exe
C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\init.dll"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
Test run - Evidence 5 of 5: Written fileSeen in the test run
b66778ea-3751-4059-a033-61fb1b205827
C:\ProgramData\Microsoft\Windows\WER\Temp\b66778ea-3751-4059-a033-61fb1b205827
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
What this file did when executed
This file was detonated in 3 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
12MITRE 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
- T1082· System recon
- T1218.011
- T1497· Sandbox evasion
- T1518.001· Checks your AV
- T1553
- T1553.002
- T1574· Execution hijack
Observed activity
Processes started
15Programs the file ran, with their command lines.
rundll32.exe"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\readme.dll",#1loaddll64.exeC:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\init.dll"cmd.exeC:\Windows\System32\cmd.exe cmd.exe /C rundll32.exe "C:\Users\user\Desktop\init.dll",#1rundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\init.dll",#1rundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe C:\Users\user\Desktop\init.dll,cs_closerundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe C:\Users\user\Desktop\init.dll,cs_disasm
Show all 15 entries for processes started
rundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe C:\Users\user\Desktop\init.dll,cs_disasm_iterrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\init.dll",cs_closerundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\init.dll",cs_disasmrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\init.dll",cs_disasm_iterrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\init.dll",cs_versionrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\init.dll",cs_supportrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\init.dll",cs_strerrorrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\init.dll",cs_regs_accessrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\init.dll",cs_reg_write
Files
15Files the file created, changed or deleted.
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\b66778ea-3751-4059-a033-61fb1b205827 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\c7aa76ba-ee18-4a84-8c4b-708bdecdffef - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\06886d06-210e-4830-9cc9-2204fa9ce152
Show all 15 entries for files
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp\223fa068-b7be-4270-a531-f28fc3fc3460 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\24423259-e130-4f1a-8e97-f41d2b9eb565 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\3cbbe7d7-2ca0-4c07-98c3-5668d0211dde - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\4865edde-94a5-4804-9abf-291195307439 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\6003b385-f386-4790-bf9a-eb1ad62c0ffd - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\7dcddb2a-bafc-4f48-8ac6-7057e8548e03 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\8af8a3c6-e3a7-4e54-9714-1f8113fc14f7 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\8e8ad75e-18d9-410c-8e20-b735798b6663 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\904e2485-55d6-4937-b444-c346d5011780
Registry and auto-start
4Settings the file changed, including ways to start again after a restart.
- Set
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\WMI\AutoLogger\Circular Kernel Context Logger\Status - Set
HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\SystemCertificates\Root\Certificates\0174E68C97DDF1E0EEEA415EA336A163D2B61AFD\Blob - Set
HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\Windows\Windows Error Reporting\Debug\StoreLocation - Set
\REGISTRY\A\{b80cb370-3474-aff8-4737-73638932f728}\Root\InventoryApplicationFile\PermissionsCheckTestKey
Mutexes
10Named locks a program uses so only one copy runs; malware families often reuse them.
\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6468\Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex5988\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6576\Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex3396\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6708\Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex6532
Show all 10 entries for mutexes
\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess3256\Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex6320\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess5756\Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex3536
Sandbox background — not the file
1The analysis machine's own processes and connections, recorded in every run.
- VM host
162.159.36.2
Chapter 04
Technical details
1 of the 70 antivirus engines that checked it flags it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 1
- CynetMalicious (score: 100)
File fingerprint
- Last analyzed
- Nov 6, 2026, 2:55 PM UTC
- SHA-256
76958e18380023a68fd1714fa2e01c594cc6db1955a07ad6937b66e66dc5d6c3- SHA-1
629ef99bda84952590b3d9f56d6f9fd05b3ee622- MD5
172be0a3a167646aa42d6c0133e082c0
About this file
capstone.dll is a Win32 DLL file of 7.6 MB.
- Type and size
- Win32 DLL · 7.6 MB
- Signer
- UnsignedNo code signature.
- First seen
- May 28, 2026On VirusTotal.
- Submitted by
- 14 distinct sources
- Packer
- None detected
- Entropy
- 3.01 of 8
First scanned
Antivirus consensus
1 of 70 engines flagged this file
5 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-235 engines0flagged
- Low-trust17 engines1flagged
View all 75 engine results
- CynetMalicious: Malicious (score: 100)
- 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
- CTXClean
- CylanceClean
- 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
- 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
- ZillyaNo result
- ZoneAlarmClean
- ZonerClean
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.
- Glasses
- GlassesCode
- Rooter
- RooterStrings
- DebuggerCheck__APIgeneric
- golang_bin_JCorn_CSC846generic
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 8 questions people ask most about this file.
Is capstone.dll a virus?
What is capstone.dll?
How many antivirus engines detected capstone.dll?
What should I do if I already used capstone.dll?
How do I remove capstone.dll?
What kind of malware is capstone.dll?
What is the SHA-256 hash of capstone.dll?
How up to date is this analysis of capstone.dll?
Community
Member reviews and reports for this exact file hash.