GridinSoft Threat Intelligence

bunx.exe threat report

Detected as Trojan.Heur! File reputation report
MD5 f70e6989d191c46d14b2b357dc4f7cf6
Latest seen 2026-05-18 02:01:03 (a week ago)
First seen 2026-05-18 02:01:03 (a week ago)
Size 110 MB
Publisher Oven
Product Bun
Signed by Codeblog CORP

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
2026-05-18 02:01:03 (a week ago)
File hash
f70e6989d191c46d14b2b357dc4f7cf6
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!, part of the Trojan threat category.

Category context

Malware disguised as legitimate software or delivered through deceptive packaging. Related Trojan reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2026-05-18 02:01:03 (a week ago); latest analysis 2026-05-18 02:01:03 (a week ago).

Publisher context

Company metadata: Oven. Product metadata: Bun.

Digital signature

Signed by Codeblog CORP. The signature is reported as valid, but signed files can still be bundled or abused.

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. Review the Trojan category for related samples and common context.

bunx.exe is a Windows file recorded in the ThreatInfo database. It is associated with Bun. The reported company name is Oven. The current detection status is Trojan.Heur!, based on the latest analysis from 2026-05-18 02:01:03 (a week ago). ThreatInfo groups this verdict with Trojan reports for broader family-level investigation.

If bunx.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: Bun
Company Name: Oven
MD5: f70e6989d191c46d14b2b357dc4f7cf6
Size: 110 MB
First Published: 2026-05-18 02:01:03 (a week ago)
Latest Published: 2026-05-18 02:01:03 (a week ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2026-05-18 02:01:03 (a week ago)
bunx.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.

Signed By: Codeblog CORP
Status: Valid

The signature on bunx.exe is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%desktop%\36keysmusic\prj\where-winds-meet-midi-player\node_modules\bun

ThreatInfo has observed bunx.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.

Windows 10 100.0%

The most common operating system signal for bunx.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.

bunx.exe is identified as pe for 64-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 64-bit
Subsystem Windows CUI
Entry point 0x03989f04
Image base 0x0000000140000000

PE Sections:

Sections 11
Raw data 115688960

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 60759040 bytes · 52.5% of section data
Large raw data
MD5 2364cbf428fdde144910a6e0d01fc25c
.rdata 47923712 bytes · 41.4% of section data
Large raw data
MD5 07435f7646955cc164770b3289587f14
.data 103936 bytes · 0.1% of section data
MD5 ec5db05864a6684d2c4ead41e2c0c776
.pdata 1457152 bytes · 1.3% of section data
MD5 0aa61064e7e983954caaf781d1b4a8d7
.fptable 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.retplne 512 bytes · 0.0% of section data
Uncommon name
MD5 bcdee87f658a7bf4080188f07db97ca9
.tls 4972544 bytes · 4.3% of section data
MD5 841a254c23209b1b5c43aad5006471ec
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 0eb01d01aace181d678cbf2a3ed04aa6
__DATA,_ 16384 bytes · 0.0% of section data
Uncommon name
MD5 ce338fe6899778aacfc28414f2d9498b
.rsrc 272384 bytes · 0.2% of section data
MD5 afdb8eb09de49f7dc721cbf800d479d1
.reloc 182272 bytes · 0.2% of section data
MD5 45a9394415a434e06791127f07aaca9c

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.

Report conclusion

GridinSoft detects this file as Trojan.Heur!

This report identifies bunx.exe by MD5 f70e6989d191c46d14b2b357dc4f7cf6. It is part of the Trojan report group. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.

Download GridinSoft Anti-Malware Scan the device and confirm whether this exact hash is present. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with f70e6989d191c46d14b2b357dc4f7cf6.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan and remove the object if the same hash is found. Use the Trojan category to compare similar reports.