Our call: Is RUNE64.dll safe?Malicious
46 of 74 engines flag this unsigned 64-bit DLL, including 10 tier-1 detections converging on VMProtect packing.
- 46 of 74 antivirus engines flagged the file, including AhnLab-V3 and Alibaba.Observed · Antivirus analysis
- The hash has a long, established submission history across 2,335 sources.Derived · Submission history
- The hash has been submitted 2,829 times from 2,335 sources.Derived · Saved report facts
a2e13fce27f1bdc920…b2fe2c9937Recommended next actions
Before using
Do not use it. Quarantine this component with your antivirus, then repair or reinstall the parent software from its official source. Do not delete or replace the component manually.
If you already used it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete46 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
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
RUNE64.dll
a2e13fce27f1bdc920aad71f43387b8ed4a7e0944b89edbcaa06aab2fe2c9937
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\library.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\RUNE64.dll"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Connect
\Device\ConDrv\\Connect
04Isolated runtime analysis
4 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
46 of 74 antivirus engines flagged the file, including AhnLab-V3 and Alibaba.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 2,335 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 2,829 times from 2,335 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: RUNE64.dll — a2e13fce27f1bdc920aad71f43387b8ed4a7e0944b89edbcaa06aab2fe2c9937
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\library.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\RUNE64.dll"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Connect — \Device\ConDrv\\Connect
ProvenanceObservedSourceIsolated runtime analysisObserved at
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
Ten tier-1 engines and 46 total detections label the file malicious, with two tier-1 engines agreeing on the VMProtect family. The DLL is unsigned, exhibits an offensive MITRE technique (T1548), and shows no trusted-publisher or clean-sandbox counter-evidence.
The engine distribution shows clear tier-1 consensus rather than low-trust-only noise. Absence of code signing removes any benign-publisher benefit. Sandbox execution reveals rundll32 abuse and an elevation-control technique, outweighing the lack of an explicit malicious sandbox verdict. Widespread but old prevalence does not mitigate the detection volume. External-intel sources add no contradictory clean signal.
What We Detected
46 of 74 engines returned malicious verdicts; 10 were tier-1 engines. Two tier-1 engines converged on the VMProtect family. The file is an unsigned 64-bit DLL first seen 392 days ago and submitted by 2335 sources.
Threat Behavior
Sandbox runs show the DLL loaded via rundll32 and the presence of MITRE technique T1548 (abuse elevation control). No dropped children or malicious host contacts were recorded, and external YARA/MalwareBazaar sources returned no hits.
What To Do Now
Do not execute or load the DLL. Keep endpoint protection enabled and quarantine the file. If found on a production system, perform a full scan and review any processes that invoked rundll32 with this library.
Where this verdict could be wrong3 caveats
- externalIntel.yaraify.ruleCount=0 and MalwareBazaar.hit=false — no independent researcher rule hits despite widespread submissions.
- behaviour.hasMaliciousSandboxVerdict=false and contactedHosts=null — sandbox did not return an explicit malicious verdict and host-reputation cross-check is unavailable.
- communityComments contain researcher verdicts but are not ground truth and may reflect the same engine detections already counted.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No dropped malicious children
- No external-intel rule hits
- Unsigned DLL
- Tier-1 consensus on VMProtect packing
- Offensive MITRE technique T1548 observed
Quarantine the file and block its hash; maintain current antivirus definitions and avoid manual execution or loading via rundll32.
Behavior
Plain-English impact first, then the observed runtime evidence.
What this file does
Observed actions and their security significance
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Note: Listed running processes; both legitimate software and malware may do this.
Note: Collects details about your system.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Threat context
How trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything 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.
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.
- \Device\ConDrv\\Connect
- \Sessions\1\BaseNamedObjects\Local\SessionImmersiveColorMutex
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Detection sources at a glance
Category: generic-trojan
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
YARA rules
No matchesThe rule pass completed without a saved public match.
46 of 74 engines flagged this file
View all 74 engine results
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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- RUNE64.dll
- Format
- Win32 DLL
- Code signing
- No verified publisher
- Size
- 13.6 MB
- Last analyzed
- Jul 30, 2026, 7:09 PM UTC
a2e13fce27f1bdc920aad71f43387b8ed4a7e0944b89edbcaa06aab2fe2c9937Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
Don't use this component. Quarantine this component with your antivirus, then repair or reinstall the parent software from its official source. Do not delete or replace the component manually.
If you already used it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
If you typed any passwords while it was open, change them from a device you trust.
Reinstall the parent software from the developer's official site instead of replacing this component by itself.