MalwareTips
Threat LensFile scan report

Is RuntimeBroker.exe safe?

Verdict
Malicious

Forty-five of 75 engines flagged this unsigned executable, while runtime evidence recorded antivirus exclusions, process injection indicators, PowerShell activity, and token manipulation.

The evidence strongly indicates a Posprefer-associated Windows trojan rather than the legitimate Windows Runtime Broker. Ten high-trust engines detected it, and execution added endpoint-protection exclusions while exhibiting T1055, T1059.001, T1134, and T1562.001 behavior.

Do not run this file

Quarantine the file and scan the system fully while keeping endpoint protection enabled. Remove unauthorized antivirus exclusions and investigate credentials, running processes, persistence, and outbound connections.

Read the full analysis
Saved file evidenceAntivirus consensus
45of 75 flagged
Flagged 45No detection 30
Digital specimenRuntimeBroker.exef083ebd45a6c488274…7e1e870c5a26fd
Size2.4 MB
Code signingUnsigned
SandboxRuntime complete
First seen7mo ago
Evidence3 priority signals
2 high-confidence signature or behavior rules matched this file.

Recommended next actions

01

Before running

Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.

02

If you already ran 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.

97%Confidence
Very high
Analyst conclusion

The evidence strongly indicates a Posprefer-associated Windows trojan rather than the legitimate Windows Runtime Broker. Ten high-trust engines detected it, and execution added endpoint-protection exclusions while exhibiting T1055, T1059.001, T1134, and T1562.001 behavior.

Where this verdict could be wrong5 caveats
  • engines.tier1FamilyConsensus.strong=false, and several engines use generic or conflicting labels rather than one strongly agreed family.
  • behaviour.hasMaliciousSandboxVerdict=false, although the completed run still recorded four offensive techniques and antivirus exclusions.
  • droppedChildren.hasMaliciousChild=false, but all nine inspected children remain unclassified rather than confirmed benign.
  • externalIntel.yaraify.ruleCount=0 and externalIntel.circl.hit=false; these absences may reflect coverage gaps rather than contradicting the engine and runtime evidence.
  • peAnalysis.likelyPacked=false and peAnalysis.highEntropyCode=false, so packing is not among the observed risk indicators.

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

Quarantine the file and scan the system fully while keeping endpoint protection enabled. Remove unauthorized antivirus exclusions and investigate credentials, running processes, persistence, and outbound connections.

Scan transparency

Coverage & freshness

4 of 5 complete

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

  • Antivirus

    Complete

    45 of 75 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Partial

    7 runtime contacts were observed without a completed reputation cross-check.

  • YARA

    Complete

    4 signature or behavior rules matched.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

Behavior

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

Runtime flight recorder

Capture complete
  • 1isolated sandbox run
  • 23MITRE ATT&CK techniques
  • 15spawned processes
  • 7network contacts
  • 23filesystem & 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: Attempted to impair or bypass security controls.

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

  • Moderate concern: Runs hidden system commands (script or shell).

  • Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.

  • Moderate concern: Scans through your files and folders.

  • Moderate concern: Decoded or unpacked concealed content while running.

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

7 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 run this file. Delete this file from the device, then empty the Recycle Bin or Trash.

  2. Recovery step 02

    If you already ran 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

    Get a fresh copy from the developer's official site or an official app store.

Safety FAQ

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

8 evidence-based answers
Is RuntimeBroker.exe malware?
Evidence-based answer
Yes — RuntimeBroker.exe is malicious. Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash. 45 of 75 antivirus engines flag it (family: Posprefer). It behaves as a trojan — malware disguised as something harmless to trick you into running it. If you've already run it, see the removal and recovery steps below.
What is RuntimeBroker.exe?
Evidence-based answer
RuntimeBroker.exe is a Windows executable program, about 2.4 MB. Our analysis identifies it as malicious (family: Posprefer) — 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 RuntimeBroker.exe?
Evidence-based answer
45 of 75 antivirus engines flagged RuntimeBroker.exe, 45 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.
I already downloaded and ran RuntimeBroker.exe — what should I do?
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 RuntimeBroker.exe?
Evidence-based answer
To remove RuntimeBroker.exe: 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) Delete this file from the device, then empty the Recycle Bin or Trash. 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 RuntimeBroker.exe?
Evidence-based answer
RuntimeBroker.exe is classified as a trojan — malware disguised as something harmless to trick you into running it. Engines attribute it to the Posprefer 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 RuntimeBroker.exe?
Evidence-based answer
The SHA-256 hash of RuntimeBroker.exe is f083ebd45a6c488274bd4a5f568eb8a6169be47a745bea92737e1e870c5a26fd, and its MD5 is 7a073336447ee31fb8bcc5347fed4954. 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 RuntimeBroker.exe?
Evidence-based answer
This report reflects the scan run on September 21, 2026. Because a file's hash never changes, the identity of RuntimeBroker.exe 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.