File scan report
Verdict Malicious
Is this Excel spreadsheet safe? No, we rate this exact file malicious.
The spreadsheet exploits CVE-2017-0199, launches an obfuscated PowerShell download chain, and exhibits credential-targeting behavior corroborated by 23 of the 62 antivirus…
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
If you already opened it, follow the steps below.
What to do now3 steps
This Excel spreadsheet is harmful. Don't open it, and delete it.
If you haven't opened it
Don't open this file. Delete it, then empty the Recycle Bin or Trash.
If you already opened it
If you already opened it, run a full antivirus scan. If it asked you to enable editing or macros and you did, also change your important passwords from another device.
If a page it opened asked for a password or card details and you entered them, change that password and call your bank.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Antivirus results
23 of 62 flagged
- Flagged 23
- No detection 39
- No result 13
- Code signing Not applicable
- Test run Completed
- First seen 12d ago
Chapter 02
Why we think so
6 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Opening this spreadsheet caused Excel to launch mshta, obfuscated PowerShell, WScript, and a downloaded executable. Twenty-three of the 62 antivirus engines that checked it flagged it, while the completed sandbox run recorded exploit and credential-targeting activity consistent with an UrcBadur-linked Office downloader.
The strongest evidence is the completed sandbox run, where Excel initiated mshta, obfuscated PowerShell, a downloaded JavaScript file, WScript, and an executable payload. Multiple major antivirus engines independently describe the document as exploiting CVE-2017-0199, and 23 of the 62 antivirus engines that checked it flagged it overall. Five malware-specific YARA rules add independent static corroboration. Although six major antivirus engines did not flag the file and all observed hosts lacked cached adverse reputation, those counter-signals do not plausibly explain the recorded exploit-driven download chain.
What We Detected
This Excel attachment was flagged by 23 of the 62 antivirus engines that checked it, including nine major detections. Avast, ESET-NOD32, Fortinet, and TrendMicro identify content associated with CVE-2017-0199, while Kaspersky and Tencent use the UrcBadur name. Five malware-specific YARA rules also matched the document.
Threat Behavior
In the completed sandbox run, Excel launched mshta.exe, followed by an obfuscated PowerShell command that downloaded JavaScript from a remote IP address. WScript then executed the downloaded script, and a separate executable payload ran from the Documents folder.
What To Do Now
Do not open the attachment or enable editing or external content. If it was opened, isolate the device from the network, keep security software enabled, and have administrators investigate the PowerShell, WScript, downloaded files, browser credentials, and any related email recipients. Reset potentially exposed credentials from a separate trusted device after containment.
Where this verdict could be wrong3 caveats
- Six major antivirus engines did not flag the file, so antivirus agreement is substantial but not universal.
- The reputation check found no cached malicious or suspicious result for any of the 18 observed hosts; host reputation can change and does not negate the recorded download chain.
- The ten dropped files have no saved verdicts, so they provide no file it created confirmation.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Six major antivirus engines did not flag the spreadsheet.
- None of the 18 observed hosts had a cached malicious or suspicious reputation result.
- Twenty-three of the 62 antivirus engines that checked it flagged the spreadsheet, including nine major detections.
- Several major engines identify an Office exploit involving CVE-2017-0199.
- Excel launched mshta, obfuscated PowerShell, WScript, and a downloaded executable during execution.
- The run recorded browser credential targeting and credential-dumping indicators.
- Five malware-specific YARA rules matched the document.
- The file presents itself as a purchase-order spreadsheet, a common social-engineering lure.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; 1 test environment rated what it did as risky.
Test run summary
Capture complete- 36sandbox rule tags
- 8spawned processes
- 15network contacts
- 40filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
High concern: Searched files where passwords and keys are stored.
High concern: Opened a browser or password-manager store that holds saved logins.
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Downloaded a file during the test run.
Moderate concern: Checked whether it was running on a test computer.
Moderate concern: Hid files or windows on the test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as password-store access, but nothing touched the Windows password store.
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
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.
Threat context
How downloaders work
This file is a delivery vehicle. On its own it can look small and harmless, but its job is to fetch and install the real payload, often a password stealer, ransomware or a bot, from a server the attacker controls.
Bottom line:Because the dangerous part arrives later, early scans can look cleaner than the threat really is.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
Excel spreadsheet
23a171bbcd02550dca16d27e20140e43be770936d0a8c30554543258135c82e5
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
EXCEL.EXE
"C:\Program Files (x86)\Microsoft Office\Office16\EXCEL.EXE" "C:\Users\<USER>\Desktop\Excel spreadsheet" /dde
Test run - Evidence 3 of 7: ProcessSeen in the test run
mshta.exe
C:\Windows\SysWOW64\mshta.exe -Embedding
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
{74D54205-AC90-4EB9-BF82-77A664311183} - OProcSessId.dat
C:\Users\<USER>\AppData\Local\Temp\{74D54205-AC90-4EB9-BF82-77A664311183} - OProcSessId.dat
Test run - Evidence 5 of 7: Written fileSeen in the test run
E5814696-C8ED-4D68-8389-AD390B0C405B
C:\Users\<USER>\AppData\Local\Microsoft\Office\16.0\WebServiceCache\AllUsers\officeclient.microsoft.com\E5814696-C8ED-4D68-8389-AD390B0C405B
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
roaming.svc.cloud.microsoft
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
boskale.me
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 36 mapped techniques, every process, file, registry and network entry and 9 dropped files.
Show the technical evidenceChapter 04
Technical details
23 of the 62 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 23
- Avast (major engine)OLE:CVE-2017-0199 [Expl]
- AVG (major engine)OLE:CVE-2017-0199 [Expl]
- DrWeb (major engine)X97M.DownLoader.2343
- ESET-NOD32 (major engine)probably Win32/Exploit.CVE-2017-0199.C trojan
- Fortinet (major engine)MSExcel/CVE_2017_0199.G1!exploit
- GData (major engine)Generic.Trojan.Agent.JIO3Q0
- Ikarus (major engine)Exploit.Office.Doc
- Kaspersky (major engine)HEUR:Trojan.OLE2.UrcBadur.genw
File fingerprint
- File name
- Excel spreadsheet
- Format
- MS Excel Spreadsheet
- Size
- 388.1 kB
- Code signing
- Not applicable to this file type
- Last analyzed
- Oct 14, 2026, 3:31 PM UTC
- SHA-256
23a171bbcd02550dca16d27e20140e43be770936d0a8c30554543258135c82e5- SHA-1
59b487a77881ece1c2bf266fdde26e858f210ef8- MD5
76186dc45d768c38795af00686a4c9e6
First scanned
Includes every engine result (75), 8 matched signature rules and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is this Excel spreadsheet malware?
What is this Excel spreadsheet?
How many antivirus engines detected this Excel spreadsheet?
I already downloaded and opened this Excel spreadsheet — what should I do?
How do I remove this Excel spreadsheet?
What kind of malware is this Excel spreadsheet?
What is the SHA-256 hash of this Excel spreadsheet?
How up to date is this analysis of this Excel spreadsheet?
Community
Member reviews and reports for this exact file hash.