Suspicious
Unsigned xlsx file with direct-IP network activity and no AV detections but rare-new prevalence.
207339d957192afad9…449d67b6b9The reasoning behind this verdict
The MT AI Engine weighs every signal from this scan — antivirus detections, sandbox behaviour, code signing, prevalence and historical matches — to reach a single, evidence-based verdict.
The complete absence of malicious detections across 66 reporting engines, including 17 tier-1 engines, is a strong clean signal. The file is an Office Open XML spreadsheet that performed ambient WMI and system-discovery calls while contacting seven Microsoft-related IPs directly. The triggered DirectIpC2 heuristic flags this pattern as suspicious because legitimate Office documents normally resolve domains. With no signing, no prior history, and rare-new prevalence, the evidence is mixed and does not reach a definitive safe or malicious threshold.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines.tier1ReportedClean=17 and engines.malicious=0
triggeredHeuristics[0].rule=MalwareTips.Synth.DirectIpC2 (direct-IP contacts without domains)
prevalence.classification=rare_new and file.ageDays=0
behaviour.hasMaliciousSandboxVerdict=false and droppedChildren.hasMaliciousChild=false
signing.signed=false with no trustedPublisher match
- 0 malicious detections across 66 engines
- 17 tier-1 engines reported clean
- No malicious sandbox verdict
- No malicious dropped children
- Unsigned file
- rare_new prevalence (0 days old)
- Direct-IP contacts without DNS (7 IPs)
Exercise caution; the file shows no confirmed malicious behaviour but exhibits an unusual direct-IP network pattern on a brand-new unsigned document.
What this file does
What it attempted when executed in an isolated sandbox
High concern: Talks to a remote server to take commands or send out your data.
Moderate concern: Checks whether it's being watched in a sandbox before acting.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
Translated from the file's technical behaviour during analysis. It never ran on your device.
What to do now
We couldn't fully clear this file. Treat it with caution.
Don't run it unless you're certain it came from a source you trust.
Check where you got it — an email attachment or a random download link is a red flag.
If you're unsure, delete it. You can always re-download a clean copy from the official source.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
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.
- 52.110.7.9
- 52.110.7.7
- 52.110.7.37
- 52.123.250.168
- 162.159.36.2
- 150.171.109.77
- 52.182.141.63
- C:\Users\<USER>\AppData\Local\Temp\{B2218A37-9C64-4789-9F36-4B36C1596ECB} - OProcSessId.dat
- C:\Users\<USER>\AppData\Local\Microsoft\Office\16.0\WebServiceCache\AllUsers\officeclient.microsoft.com\AF5ADC8A-62B7-461C-8A3D-FAE15182959B
- C:\Users\<USER>\AppData\Local\Microsoft\Office\16.0\excel.exe_Rules.xml
- C:\Users\<USER>\Desktop\~$Invoice Details - 640274.xlsx
- C:\Users\<USER>\Desktop\Invoice Details - 640274.xlsx
- C:\Users\<USER>\AppData\Roaming\Microsoft\Office\Recent\Invoice Details - 640274.xlsx.LNK
- C:\Users\<USER>\AppData\Local\Microsoft\Schemas\MS Excel_restart.xml
- C:\Users\<USER>\AppData\Roaming\Microsoft\Office\Recent\Cover-letter-writing-guide-Nov-12-2015.docx.LNK
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- Local\10MU_ACBPIDS_S-1-5-5-0-152860
- Local\10MU_ACB10_S-1-5-5-0-152860
- Global\552FFA80-3393-423d-8671-7BA046BB5906
- Local\F99C425F-9135-43ed-BD7D-396DE488DC53_Office16
- Global\MTX_MSO_Formal1_S-1-5-21-4005801669-2598574594-602355426-1001
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- 6f57919a0016f7e10ef4…3b9650Never scannednever seen before
- 97da3c982874ec87dcba…014346Never scannednever seen before
- a5df65ab882ede03cc21…9f9e94Never scannednever seen before
- c88a0b907419a70c27ab…94aecfNever scannednever seen before
YARA & heuristic rule matches
One or more medium-severity heuristic rules matched. Not definitive, but the patterns match known malware behaviour.
Sample contacted 7 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence52.110.7.9 · 52.110.7.7 · 52.110.7.37
0 detections across 74 engines
How widely this file has been seen
Barely seen in the wild and first surfaced recently. This is the footprint of targeted malware the AV industry hasn't signatured yet — extra scrutiny is warranted.
Forensic fingerprint
- File name
- bdnwrtn.exe
- Size
- 10.0 KB
- MIME type
- (unknown)
- Detected type
- Office Open XML Spreadsheet
- SHA-256
- 207339d957192afad9940870715d63ba0e478e49a9551d9434cd17449d67b6b9
- MD5
- 794ba71413d90ccc0f52bab439d47bbc
- SHA-1
- 64836549b3b578bfdffe747c986c46f4ca4b9055
- First seen (VT)
- 7/13/2026, 4:58:15 AM
- Last analysis (VT)
- 7/13/2026, 4:58:15 AM
- First scan (MalwareTips)
- 7/13/2026, 5:07:05 AM
- Last scan (MalwareTips)
- 7/13/2026, 5:07:05 AM
Safety FAQ
Common questions about bdnwrtn.exe, answered from the scan data above.
- bdnwrtn.exe is suspicious — treat it as unsafe until you're sure. 0 of 74 antivirus engines flag it, which isn't a strong consensus but is enough to be cautious. Don't run it unless you fully trust where it came from, and prefer downloading the software fresh from its official site.
- bdnwrtn.exe is a Windows executable program, about 10 KB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
- None — all 74 antivirus engines we queried report bdnwrtn.exe as clean. That's reassuring, though brand-new malware can briefly evade detection before vendors add signatures, so we also weigh the file's behaviour and reputation.
- 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.
- To remove bdnwrtn.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 the original bdnwrtn.exe file and empty the Recycle Bin/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.
- The SHA-256 hash of bdnwrtn.exe is 207339d957192afad9940870715d63ba0e478e49a9551d9434cd17449d67b6b9, and its MD5 is 794ba71413d90ccc0f52bab439d47bbc. 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.
- This report reflects the scan run on July 13, 2026. Because a file's hash never changes, the identity of bdnwrtn.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.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.