Is bdnwrtn.exe safe?
Suspicious file assessment
0 of 74 antivirus engines flagged the file.
207339d957192afad9…cd17449d67b6b9Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial7 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 7MITRE ATT&CK techniques
- 4spawned processes
- 7network contacts
- 32filesystem & mutex artifacts
What this file does
Observed actions and their security significance
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Reads your Windows user-account details.
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.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
bdnwrtn.exe
207339d957192afad9940870715d63ba0e478e49a9551d9434cd17449d67b6b9
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Windows\system32\services.exe
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files (x86)\Microsoft Office\Office16\EXCEL.EXE" "C:\Users\<USER>\Desktop\Invoice Details - 640274.xlsx" /dde
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
{B2218A37-9C64-4789-9F36-4B36C1596ECB} - OProcSessId.dat
C:\Users\<USER>\AppData\Local\Temp\{B2218A37-9C64-4789-9F36-4B36C1596ECB} - OProcSessId.dat
04Isolated runtime analysis - Written fileObserved
AF5ADC8A-62B7-461C-8A3D-FAE15182959B
C:\Users\<USER>\AppData\Local\Microsoft\Office\16.0\WebServiceCache\AllUsers\officeclient.microsoft.com\AF5ADC8A-62B7-461C-8A3D-FAE15182959B
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
52.110.7.9
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
52.110.7.7
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
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
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 0 / 74engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 74 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: bdnwrtn.exe — 207339d957192afad9940870715d63ba0e478e49a9551d9434cd17449d67b6b9
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Program Files (x86)\Microsoft Office\Office16\EXCEL.EXE" "C:\Users\<USER>\Desktop\Invoice Details - 640274.xlsx" /dde
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: {B2218A37-9C64-4789-9F36-4B36C1596ECB} - OProcSessId.dat — C:\Users\<USER>\AppData\Local\Temp\{B2218A37-9C64-4789-9F36-4B36C1596ECB} - OProcSessId.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: AF5ADC8A-62B7-461C-8A3D-FAE15182959B — C:\Users\<USER>\AppData\Local\Microsoft\Office\16.0\WebServiceCache\AllUsers\officeclient.microsoft.com\AF5ADC8A-62B7-461C-8A3D-FAE15182959B
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 52.110.7.9 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 52.110.7.7 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence52.110.7.9 · 52.110.7.7 · 52.110.7.37
0 of 74 engines flagged this file
View all 74 engine results
PE structure
Not runThis looks like a Windows executable, but no completed PE structure result is saved.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- bdnwrtn.exe
- Format
- Office Open XML Spreadsheet
- Code signing
- No verified publisher
- Size
- 10.0 KB
- Last analyzed
- Jul 13, 2026, 9:07 AM UTC
207339d957192afad9940870715d63ba0e478e49a9551d9434cd17449d67b6b9Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is bdnwrtn.exe safe, or is it malware?
What is bdnwrtn.exe?
How many antivirus engines detected bdnwrtn.exe?
What should I do if I already ran bdnwrtn.exe?
How do I remove bdnwrtn.exe?
What is the SHA-256 hash of bdnwrtn.exe?
How up to date is this analysis of bdnwrtn.exe?
Community
Member reviews and reports for this exact file hash.