MalwareTips
Threat LensFile scan report

Is RUNE64.dll safe?

Verdict
Malicious

Unsigned DLL with eight tier-1 detections and runtime evidence mapped to T1055 process-injection behavior.

38 of 75 engines flag the file, including eight tier-1 engines. The DLL is unsigned, exhibits T1055 process injection, and shows no contradictory clean signals.

Do not use this component

Block the file and investigate any systems where it has already been executed.

Read the full analysis
Saved file evidenceAntivirus consensus
38of 75 flagged
Flagged 38No detection 37
Digital specimenRUNE64.dll558f78598eefc0d042…796a6b67ef76eb
Size2.2 MB
Code signingUnsigned
SandboxRuntime complete
First seen12d ago
Evidence3 priority signals
1 high-confidence signature or behavior rule matched this file.

Recommended next actions

01

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.

02

If you already used it

Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

82%Confidence
High
Analyst conclusion

38 of 75 engines flag the file, including eight tier-1 engines. The DLL is unsigned, exhibits T1055 process injection, and shows no contradictory clean signals.

Where this verdict could be wrong1 caveat
  • prevalence.classification=common_new with 1264 submitters suggests wide distribution, which can occur with both commodity software and malware.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

Recommended action

Block the file and investigate any systems where it has already been executed.

Scan transparency

Coverage & freshness

3 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    38 of 75 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Not run

    No contacted-host reputation check is recorded.

    No timestamp recorded

  • YARA

    Complete

    1 signature or behavior rule matched.

  • External intel

    Partial

    Independent reference checks were attempted but are incomplete.

Chapter 03

Behavior

Plain-English impact first, then the observed runtime evidence.

Runtime flight recorder

Capture complete
  • 1isolated sandbox run
  • 10MITRE ATT&CK techniques
  • 7spawned processes
  • 0network contacts
  • 1filesystem & mutex artifacts

What this file does

Observed actions and their security significance

  • High concern: Injected code into another process, a technique that can conceal execution.

  • High concern: Manipulated how the operating system loads code, which can redirect execution.

  • Moderate concern: Contained obfuscated or packed code that makes inspection harder.

  • Moderate concern: Checked the environment for virtualisation or analysis tools.

  • Note: Reads your Windows user-account details.

  • 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.

Recorded behavior

Attack story

Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.

ObservedDerived

4 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.

Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & 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.

  1. Recovery step 01

    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.

  2. Recovery step 02

    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.

  3. Recovery step 03

    If you typed any passwords while it was open, change them from a device you trust.

  4. Recovery step 04

    Reinstall the parent software from the developer's official site instead of replacing this component by itself.

Safety FAQ

Direct answers grounded in the saved verdict and evidence in this report.

8 evidence-based answers
Is RUNE64.dll a virus?
Evidence-based answer
Yes — RUNE64.dll is malicious. 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. 38 of 75 antivirus engines flag it (family: kepavll). It behaves as a trojan — malware disguised as something harmless to trick you into running it. If you've already used it, see the removal and recovery steps below.
What is RUNE64.dll?
Evidence-based answer
RUNE64.dll is a Windows library or loadable module, about 2.2 MB. Our analysis identifies it as malicious (family: kepavll) — a trojan — malware disguised as something harmless to trick you into running it. Because a file's name and icon can be faked, the safest way to identify it is by its cryptographic hash (below), not its filename.
How many antivirus engines detected RUNE64.dll?
Evidence-based answer
38 of 75 antivirus engines flagged RUNE64.dll, 38 of them as outright malicious. The raw count alone does not establish safety or danger; we also weigh which engines flagged it and corroborating behavior, identity, reputation, and rule evidence. The malicious verdict comes from the complete saved evidence, not from this antivirus count by itself.
What should I do if I already used RUNE64.dll?
Evidence-based answer
Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
How do I remove RUNE64.dll?
Evidence-based answer
To remove RUNE64.dll: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) 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. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
What kind of malware is RUNE64.dll?
Evidence-based answer
RUNE64.dll is classified as a trojan — malware disguised as something harmless to trick you into running it. Engines attribute it to the kepavll family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
What is the SHA-256 hash of RUNE64.dll?
Evidence-based answer
The SHA-256 hash of RUNE64.dll is 558f78598eefc0d042d772fbf5e86e45f5fb5c5b47e7a5ef96796a6b67ef76eb, and its MD5 is 6951b0bae9b06ea933cea97365d286a4. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
How up to date is this analysis of RUNE64.dll?
Evidence-based answer
This report reflects the scan run on August 5, 2026. Because a file's hash never changes, the identity of RUNE64.dll is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Scan another
Check a different file
URL instead?
Check if a link is safe
The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.