File scan report
Verdict Suspicious
Is this Word document safe? Treat it as suspicious.
This Word document has no antivirus detections, but a public malware-sharing listing, one community YARA rule and a split sandbox result leave its status unresolved.
Read the whole reasonShow less
Why Suspicious? It is listed in MalwareBazaar, a public database that accepts automated uploads and a community rule for known malware matched it.
Moderate evidence · More than one sign points to a problem, but nothing confirms it is harmful.
Don't open links in it until the sender confirms they sent it, using contact details you already have.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't open it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm who sent it, delete it, or ask the sender to confirm they sent it.
If you already opened it
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.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
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 10
- Code signing Not applicable
- Test run Completed
- First seen 18d ago
Chapter 02
Why we think so
3 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 65 antivirus engines that checked it flagged this Word document, and its activity in the test run looked like ordinary Word use. It is listed in a public malware-sharing database without a named family and matched one community YARA rule. One sandbox run returned malicious while another returned clean. That leaves too little evidence to call it either way.
Engine coverage is adequate, and no engine flagged the file, including all 18 major antivirus engines that reported. The hash appears in a public sample-sharing database that anyone can submit to; the entry came from an anonymous reporter and names no family. One community YARA rule matched, describing an unnamed family, which is a lead rather than confirmation. The sandbox runs disagreed. The recorded activity shows only Word processes, Office template and cache writes, and connections to Microsoft Office services, with no named injection target. The injection and encryption technique labels were mapped without any matching activity being recorded.
What We Detected
None of the 65 antivirus engines that checked it flagged this Word document. The hash is listed in a public malware-sharing database without a named family. It matched one community YARA rule that describes an unidentified family.
Threat Behavior
The sandbox runs disagreed: one returned malicious and another returned clean. The recorded activity was Word opening the document, writing Office templates and cache files, setting font registry entries and contacting Microsoft Office services. None of the contacted hosts are known to be malicious. No process injection target or file encryption was observed.
What To Do Now
If you did not expect this document, confirm with the sender through a separate channel before opening it. Keep macros and editing disabled in Protected View, and keep your antivirus enabled.
Where this verdict could be wrong2 caveats
- No antivirus engine flags the document, and the observed activity looks like Word opening a file, so the listing and the split sandbox run may be noise.
- A single community YARA rule naming an unknown family is a weak lead and may reflect a broad pattern match.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 65 antivirus engines that checked it flagged the file
- Another sandbox run returned clean, and the observed activity matches normal Word behaviour
- No contacted host is known to be malicious
- Listed in a public malware-sharing database (no family named)
- Matched one community YARA rule describing an unidentified malware family
- One sandbox run returned a malicious result
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- 10sandbox rule tags
- 2spawned processes
- 5network contacts
- 29filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
High concern: Encrypted files on the test computer, as ransomware does.
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
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.
Note: Looked through folders on the test computer (most installers do this).
Sandbox labels we could not confirm (common in safe files too)
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 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.
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
Word document
faf48d06765f7d2f06362e262f33a2f8db89fe857b39f8697d584e43d8c15325
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
WINWORD.EXE
"C:\Program Files (x86)\Microsoft Office\Office16\WINWORD.EXE" "C:\Users\<USER>\Desktop\Word document" /q
Test run - Evidence 3 of 7: ProcessSeen in the test run
WINWORD.EXE
C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE "C:\Program Files\Microsoft Office\Root\Office16\WINWORD.EXE" /Automation -Embedding
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
{6C0B618A-4A92-4EF1-BB63-8DF71A9FA7F8} - OProcSessId.dat
C:\Users\<USER>\AppData\Local\Temp\{6C0B618A-4A92-4EF1-BB63-8DF71A9FA7F8} - OProcSessId.dat
Test run - Evidence 5 of 7: Written fileSeen in the test run
895D5C51-3306-45AC-9DA9-A366A7F281E6
C:\Users\<USER>\AppData\Local\Microsoft\Office\16.0\WebServiceCache\AllUsers\officeclient.microsoft.com\895D5C51-3306-45AC-9DA9-A366A7F281E6
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
templateservice.office.com
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
What this file did when executed
The combined sandbox summary is split: at least one run returned "malicious" and another returned "clean".
Sandbox verdicts
2- VT: MALWAREmalicious
- VT: CLEANclean
Techniques observed in the sandbox
10MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1033· Reads user info
- T1055· Process injection
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1221
- T1486· File encryption
- T1497· Sandbox evasion
- T1574· Execution hijack
Observed activity
Processes started
2Programs the file ran, with their command lines.
WINWORD.EXE"C:\Program Files (x86)\Microsoft Office\Office16\WINWORD.EXE" "C:\Users\<USER>\Desktop\Word document" /qWINWORD.EXEC:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE "C:\Program Files\Microsoft Office\Root\Office16\WINWORD.EXE" /Automation -Embedding
Network contacts
55 hosts, listed as 3 domains, 2 addresses, 1 link. Links show the host and path only.
- Domain
roaming.svc.cloud.microsoft - Domain
templateservice.office.com - Domain
atm.office.mira.tm.svc.cloud.microsoft - IP address
52.110.6.7 - IP address
52.110.7.6 - URL
https://roaming.svc.cloud.microsoft/rs/RoamingSoapService.svc
Files
18Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\{6C0B618A-4A92-4EF1-BB63-8DF71A9FA7F8} - OProcSessId.dat - Written
C:\Users\<USER>\AppData\Local\Microsoft\Office\16.0\WebServiceCache\AllUsers\officeclient.microsoft.com\895D5C51-3306-45AC-9DA9-A366A7F281E6 - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Templates\Normal.dotm - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Templates\~$Normal.dotm - Written
C:\Users\<USER>\AppData\Local\Microsoft\Office\16.0\winword.exe_Rules.xml - Written
C:\Users\<USER>\Desktop\Word document
Show all 18 entries for files
- Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Office\Recent\Word document.LNK - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Office\Recent\index.dat - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\UProof\CUSTOM.DIC - Written
C:\Users\<USER>\AppData\Local\Temp\cab1E8B.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\cab1E8C.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\cab1E8F.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\cab1EA2.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\cab1EA6.tmp - Deleted
C:\Users\<USER>\AppData\Roaming\Microsoft\Office\Recent\Word document.LNK - Deleted
C:\Users\<USER>\AppData\Local\Microsoft\Schemas\MS Word_restart.xml - Deleted
C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin - Deleted
C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
Registry and auto-start
15Settings the file changed, including ways to start again after a restart.
- Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\Batang - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\Dotum - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\SimHei - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\Gulim - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\Angsana New - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\Cordia New
Show all 15 entries for registry and auto-start
- Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\Gautami - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\DengXian - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\HCR Dotum - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\HCR Dotum Ext - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\HCR Batang - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\HCR Batang Ext - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\HCR Batang ExtB - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\HyhwpEQ - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Panose\HancomEQN
Mutexes
9Named locks a program uses so only one copy runs; malware families often reuse them.
Local\10MU_ACBPIDS_S-1-5-5-0-158617Local\10MU_ACB10_S-1-5-5-0-158617Global\552FFA80-3393-423d-8671-7BA046BB5906Local\2BF388D5-6F8C-40A0-A7EE-996D005C4E14_Office16Local\F99C425F-9135-43ed-BD7D-396DE488DC53_Office16Global\MTX_MSO_Formal1_S-1-5-21-4005801669-2598574594-602355426-1001
Show all 9 entries for mutexes
Global\MTX_MSO_AdHoc1_S-1-5-21-4005801669-2598574594-602355426-10015CAC3FAB-87F0-4750-984D-D50144543427Office-VER16Local\SessionImmersiveColorMutex
Sandbox background — not the file
3The analysis machine's own processes and connections, recorded in every run.
- VM process
services.exeC:\Windows\system32\services.exe - VM process
Explorer.EXEC:\Windows\Explorer.EXE - VM host
162.159.36.2
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache. 5 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 232f4854a70cfa982352…f4b096Not checkedno saved verdict
- 97da3c982874ec87dcba…014346Not checkedno saved verdict
- 58c69c8a5dccf9a8b7a5…9f0eb8Not checkedno saved verdict
- d96f7a63a912ca058fb1…7faeddNot checkedno saved verdict
- c88a0b907419a70c27ab…94aecfNot checkedno saved verdict
Chapter 04
Technical details
None of the 65 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.
File fingerprint
- File name
- Word document
- Format
- Office Open XML Document
- Size
- 34.6 kB
- Code signing
- Not applicable to this file type
- Last analyzed
- Oct 11, 2026, 8:27 AM UTC
- SHA-256
faf48d06765f7d2f06362e262f33a2f8db89fe857b39f8697d584e43d8c15325- SHA-1
7099126ab6d469e203fce750d571c2fd9bba371b- MD5
3f7d7ee50786368466a7adf7fcaddec7
First scanned Updated
Verdict history
- Malicious
- Suspiciousafter a re-check of the saved evidence
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Antivirus consensus
0 of 65 engines flagged this file
10 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-234 engines0flagged
- Low-trust13 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastClean
- Avast-MobileClean
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DeepInstinctNo result
- DrWebClean
- ElasticNo result
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineNo result
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
- MULTI_Malware_Unknown_ForgeAuto_4f67e0b3_Extrait
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
Is this Word document safe, or is it malware?
What is this Word document?
How many antivirus engines detected this Word document?
I already downloaded and opened this Word document — what should I do?
Has this Word document been seen before?
What is the SHA-256 hash of this Word document?
How up to date is this analysis of this Word document?
Community
Member reviews and reports for this exact file hash.