Runtime Broker.exe threat report

MD5 479f6bf97b03d9e4badc095f466a4342
Latest seen 2024-08-24 23:02:17 (2 years ago)
First seen 2024-08-24 23:02:17 (2 years ago)
Size 132 MB
Publisher GitHub, Inc.

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Trojan.Heur!
Recommended action
Scan and remove
Last analysis
2024-08-24 23:02:17 (2 years ago)
File hash
479f6bf97b03d9e4badc095f466a4342
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2024-08-24 23:02:17 (2 years ago); latest analysis 2024-08-24 23:02:17 (2 years ago).

Publisher context

Company metadata: GitHub, Inc.. Product metadata: NVIDIA Control Panel.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

Runtime Broker.exe is a Windows file recorded in the ThreatInfo database. It is associated with NVIDIA Control Panel. The reported company name is GitHub, Inc.. The current detection status is Trojan.Heur!, based on the latest analysis from 2024-08-24 23:02:17 (2 years ago).

If Runtime Broker.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Trojan.Heur!.

Product Name: NVIDIA Control Panel
Company Name: GitHub, Inc.
MD5: 479f6bf97b03d9e4badc095f466a4342
Size: 132 MB
First Published: 2024-08-24 23:02:17 (2 years ago)
Latest Published: 2024-08-24 23:02:17 (2 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2024-08-24 23:02:17 (2 years ago)
Runtime Broker.exe detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

%localappdata%\microsoft\vault\log

ThreatInfo has observed Runtime Broker.exe in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

100.0%

The strongest geographic signal for this file is The Netherlands with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

The most common operating system signal for Runtime Broker.exe is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

Runtime Broker.exe is identified as pe for 32 systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x00400000
Entry Address: 0x037c4cb0

PE Sections:

Name Size of data MD5
.text 111944192 82e7695dd00986cd812484781842486b
.rdata 21714944 866341acdbfcde723a1098a78401f55f
.data 388096 dfcaca3def08e6006f8207a4de661d41
.00cfg 512 cf4e5f05457a87d03ad770258959ced3
.rodata 2560 cce326712ebe143ce83eff8afbdba7b9
.tls 512 c63553d40fa6ee68787f8dd857037999
CPADinfo 512 842689af09e7bf563672a4b43f1a2286
malloc_h 1536 d3dd1d055977a3943272d82767800f3c
.rsrc 210944 003c683a547e64345ca64fcaf81e409e
.reloc 4168192 2a10dd5d7801e2f1618d5aad2ff724af

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

More information: