MalwareTips

File scan report

Scan another file

Verdict Suspicious

Analyzed , 3 months ago

Is bdnwrtn.exe safe? Treat it as suspicious.

Unsigned xlsx file with direct-IP network activity and no AV detections but rare-new prevalence.

Why Suspicious? Unsigned file.

Limited evidence · One sign points to a problem; nothing else confirms it.

Don't run it until you know where it came from

Exercise caution; the file shows no confirmed malicious behaviour but exhibits an unusual direct-IP network pattern on an unsigned document.

What to do now4 steps

Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.

What to do

  1. Don't run it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.

If you already ran it

  1. Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.

Not sure what to do?

Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.

Paste this report's link in your topic so helpers can see what was found.

Why we think so

Share this file report

bdnwrtn.exe: Suspicious — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

0 of 65 flagged

  • Flagged 0
  • No detection 65
  • No result 9
Filebdnwrtn.exe10.3 kBSHA-256 207339d95719…67b6b9
  • Code signing Unsigned
  • Test run Completed
  • First seen 3mo ago
None of the 65 antivirus engines that checked it flag it.

Chapter 02

Why we think so

3 points against it and 2 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

The sample is unsigned, only one day old, and triggered a rule for contacting seven external IPs without using DNS. Sandbox analysis found no malicious behaviour and no malicious files it created were dropped.

Where this verdict could be wrong1 caveat
  • Direct-IP contacts (52.110.7.9, 52.110.7.7, etc.) without DNS resolution is unusual for benign Office documents and could indicate a control server, but sandbox returned no malicious verdict.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

6 sources checked · 5 complete · 1 partial. See every source

Chapter 03

What it did in our test

It ran in our isolated test environment; no test environment rated what it did as risky.

Test run summary

Capture complete
  • 7sandbox rule tags
  • 2spawned processes
  • 6network contacts
  • 32filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • Moderate concern: Checked whether it was running on a test computer.

  • Note: Read the user name of the test computer.

  • Note: Talked to servers over the internet during the test run.

  • Note: Read basic details of the test computer, such as its Windows version.

This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.

Recorded behavior

What happened in the test

Grouped by step. The order is not a timeline.

Seen in the test runWorked out from other results

  1. Input file

    The submitted object

    1
    1. Evidence 1 of 7: FileSeen in the test run

      bdnwrtn.exe

      207339d957192afad9940870715d63ba0e478e49a9551d9434cd17449d67b6b9

      Uploaded file

  2. Processes

    What ran

    2
    1. Evidence 2 of 7: ProcessSeen in the test run

      EXCEL.EXE

      "C:\Program Files (x86)\Microsoft Office\Office16\EXCEL.EXE" "C:\Users\<USER>\Desktop\Invoice Details - 640274.xlsx" /dde

      Test run
    2. Evidence 3 of 7: ProcessSeen in the test run

      EXCEL.EXE

      C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE "C:\Program Files\Microsoft Office\Root\Office16\EXCEL.EXE" /automation -Embedding

      Test run
    3. +1 more recorded observation

  3. Files

    Created or changed

    2
    1. Evidence 4 of 7: Written fileSeen in the test run

      {B2218A37-9C64-4789-9F36-4B36C1596ECB} - OProcSessId.dat

      C:\Users\<USER>\AppData\Local\Temp\{B2218A37-9C64-4789-9F36-4B36C1596ECB} - OProcSessId.dat

      Test run
    2. Evidence 5 of 7: Written fileSeen in the test run

      AF5ADC8A-62B7-461C-8A3D-FAE15182959B

      C:\Users\<USER>\AppData\Local\Microsoft\Office\16.0\WebServiceCache\AllUsers\officeclient.microsoft.com\AF5ADC8A-62B7-461C-8A3D-FAE15182959B

      Test run
    3. +1 more recorded observation

  4. Network

    Hosts contacted

    2
    1. Evidence 6 of 7: Contacted hostSeen in the test run

      52.110.7.9

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostSeen in the test run

      52.110.7.7

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

7 facts from the test run. See the full activity list.

Chapter 04

Technical details

None of the 65 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 74 enginesCompletePositive signal: 0 of 65 engines flagged it · 9 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial6 hosts contacted in the test run had no completed reputation check Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesCompleteNo rule matched
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

File fingerprint

Last analyzed
Jul 13, 2026, 9:07 AM UTC
SHA-256
207339d957192afad9940870715d63ba0e478e49a9551d9434cd17449d67b6b9
SHA-1
64836549b3b578bfdffe747c986c46f4ca4b9055
MD5
794ba71413d90ccc0f52bab439d47bbc

About this file

bdnwrtn.exe is an Office Open XML Spreadsheet file of 10.3 kB.

Type and size
Office Open XML Spreadsheet · 10.3 kB
Signer
UnsignedNo code signature.
First seen
Jul 13, 2026On VirusTotal.
Submitted by
1 sourceRarely seen: few people have submitted this exact file.

First scanned

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is bdnwrtn.exe safe, or is it malware?
bdnwrtn.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. No antivirus engine flags it; the caution comes from other evidence, such as who made it, how widely it is used or what it did in a test run. Don't run it unless you're sure where it came from. If you need the program, download it again from the publisher's own website.
What is bdnwrtn.exe?
bdnwrtn.exe is a Windows program, about 10.3 kB. VirusTotal first saw it on Jul 13, 2026.
How many antivirus engines detected bdnwrtn.exe?
None of the 65 antivirus engines that checked it flag bdnwrtn.exe. A clean antivirus result is not proof of safety; the caution comes from other evidence, such as who made it, how widely it is used or what it did in a test run.
What should I do if I already ran bdnwrtn.exe?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
What is the SHA-256 hash of bdnwrtn.exe?
The SHA-256 fingerprint of bdnwrtn.exe is 207339d957192afad9940870715d63ba0e478e49a9551d9434cd17449d67b6b9, and its MD5 is 794ba71413d90ccc0f52bab439d47bbc. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of bdnwrtn.exe?
This report reflects the scan on Jul 13, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Related file reports

Recent reports on other files with the same rating.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.