File scan report
Verdict Suspicious
Is Obwiess TPMSpoofer. exe safe? Treat it as suspicious.
Unsigned 64-bit executable with three major detections but no strong family consensus or malicious sandbox behaviour.
Read the whole reasonShow less
Why Suspicious? 18 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Treat as suspicious pending further analysis; do not execute without additional verification.
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 run 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 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
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
18 of 71 flagged
- Flagged 18
- No detection 53
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 4mo ago
Chapter 02
Why we think so
3 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
No sandbox malice, no dropped malicious files it created, and no external-intel corroboration were observed.
The file triggered three major detections (Fortinet, Symantec, TrendMicro-HouseCall) but the labels remain generic and lack a strong family consensus. The executable is unsigned, which is a risk factor for a 9 MB PE, yet the single sandbox run produced no malicious verdict and no offensive MITRE techniques. Medium prevalence and absence of external-intel hits keep the sample in mixed-signal territory rather than a clear malicious classification.
What We Detected
18 of the 71 antivirus engines that checked it flagged the sample, including three major antivirus engines. Detections are generic (PossibleThreat, ML.Attribute.HighConfidence, Trojan.Win64.Gen) with no named family agreed upon by multiple major antivirus engines.
Threat Behavior
The file is unsigned. Sandbox execution showed only techniques common in legitimate software and no malicious verdict. No domains, IPs, or URLs were contacted, and the single file it created was not flagged malicious.
What To Do Now
Do not run the file. Keep security software enabled. If the file is required, submit it to a controlled analysis environment or request additional vendor review before execution.
- no malicious sandbox verdict
- no external-intel hits
- unsigned executable
- three major detections
- medium prevalence
6 sources checked · 5 complete · 1 not needed or not applicable. 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- 13sandbox rule tags
- 3spawned processes
- 0network contacts
- 5filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
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).
Note: Loaded extra code modules while running.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
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 5: FileSeen in the test run
ObwiessTPMSpoofer.exe
aebb6ef772be59d710d89ea46b1fafd07a8a628d9e5f494b932caa917bcc1c3b
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
cmd.exe
cmd.exe /d /c exit 0
Test run - Evidence 3 of 5: ProcessSeen in the test run
ObwiessTPMSpoofer.exe
"C:\Users\user\Desktop\ObwiessTPMSpoofer.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
obwiess_preflight_00000AD8.tmp
C:\Users\<USER>\AppData\Local\Temp\obwiess_preflight_00000AD8.tmp
Test run - Evidence 5 of 5: Written fileSeen in the test run
obwiess_preflight_00001B54.tmp
C:\Users\user\AppData\Local\Temp\obwiess_preflight_00001B54.tmp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
13MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1010
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1027.005· Obfuscated code
- T1056· Keylogging
- T1056.001· Keylogging
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1115
- T1129· Loads modules
- T1222
- T1614
Observed activity
Processes started
3Programs the file ran, with their command lines.
cmd.execmd.exe /d /c exit 0ObwiessTPMSpoofer.exe"C:\Users\user\Desktop\ObwiessTPMSpoofer.exe"cmd.exeC:\Windows\System32\cmd.exe cmd.exe /d /c exit 0
Files
5Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\obwiess_preflight_00000AD8.tmp - Written
C:\Users\user\AppData\Local\Temp\obwiess_preflight_00001B54.tmp - Written
\Device\ConDrv\\Connect - Deleted
C:\Users\<USER>\AppData\Local\Temp\obwiess_preflight_00000AD8.tmp - Deleted
C:\Users\user\AppData\Local\Temp\obwiess_preflight_00001B54.tmp
Sandbox background — not the file
1The analysis machine's own processes and connections, recorded in every run.
- VM process
conhost.exeC:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache. 1 has no saved verdict and was not checked; that is missing coverage, not a finding.
- fc490038819b5e0a4664…dba40aNot checkedno saved verdict
Chapter 04
Technical details
18 of the 71 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 18
- Fortinet (major engine)W32/PossibleThreat
- Symantec (major engine)ML.Attribute.HighConfidence
- TrellixENS (major engine)Artemis!06D44B972A1D
- TrendMicro-HouseCall (major engine)Trojan.Win64.Gen.TL0101FT26ZJ
- APEXMalicious
- BkavW32.Malware.F08DF73A
- CrowdStrikewin/malicious_confidence_70% (W)
- CTXexe.trojan.generic
File fingerprint
- Last analyzed
- Aug 30, 2026, 11:33 PM UTC
- SHA-256
aebb6ef772be59d710d89ea46b1fafd07a8a628d9e5f494b932caa917bcc1c3b- SHA-1
2eedf3c3eb574e8cc8b2bc6f4bb2ff6c2db99b7a- MD5
06d44b972a1d2e56fa470d7323563b3f
About this file
ObwiessTPMSpoofer.exe is a Win32 EXE file of 9.0 MB.
- Type and size
- Win32 EXE · 9.0 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jun 27, 2026On VirusTotal.
- Submitted by
- 23 distinct sources
- Packer
- None detected
- Entropy
- 6.88 of 8
First scanned
Antivirus consensus
18 of 71 engines flagged this file
4 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.
The 18 detections come from 17 independent scan engines: several vendors license the same engine, so their results are one vote.
- Tier-118 engines4flagged
- Tier-236 engines7flagged
- Low-trust17 engines7flagged
View all 75 engine results
- APEXMalicious: Malicious
- BkavMalicious: W32.Malware.F08DF73A
- CrowdStrikeMalicious: win/malicious_confidence_70% (W)
- CTXMalicious: exe.trojan.generic
- CynetMalicious: Malicious (score: 100)
- DeepInstinctMalicious: MALICIOUS
- ElasticMalicious: malicious (high confidence)
- FortinetMalicious: W32/PossibleThreat
- LionicMalicious: Trojan.Win32.Generic.4!c
- MaxSecureMalicious: Trojan.Malware.8328611.susgen
- McAfeeDMalicious: ti!AEBB6EF772BE
- PaloaltoMalicious: generic.ml
- RisingMalicious: Trojan.Kryptik@AI.94 (RDML:t86lYv8/hOZSXLU0ON/87Q)
- SangforMalicious: Trojan.Win32.Save.a
- SentinelOneMalicious: Static AI - Suspicious PE
- SymantecMalicious: ML.Attribute.HighConfidence
- TrellixENSMalicious: Artemis!06D44B972A1D
- TrendMicro-HouseCallMalicious: Trojan.Win64.Gen.TL0101FT26ZJ
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CylanceClean
- DrWebClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- MalwarebytesClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PandaClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrendMicroClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
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 6 questions people ask most about this file.
Is ObwiessTPMSpoofer.exe safe, or is it malware?
What is ObwiessTPMSpoofer.exe?
How many antivirus engines detected ObwiessTPMSpoofer.exe?
I already downloaded and ran ObwiessTPMSpoofer.exe — what should I do?
What is the SHA-256 hash of ObwiessTPMSpoofer.exe?
How up to date is this analysis of ObwiessTPMSpoofer.exe?
Community
Member reviews and reports for this exact file hash.