Is ObwiessTPMSpoofer.exe safe?
Unsigned 64-bit executable with three tier-1 detections but no strong family consensus or malicious sandbox behaviour.
Three tier-1 engines flagged the file with generic threat labels while 14 tier-1 engines reported it clean. No sandbox malice, no dropped malicious children, and no external-intel corroboration were observed.
aebb6ef772be59d710…2caa917bcc1c3bRecommended 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.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
Three tier-1 engines flagged the file with generic threat labels while 14 tier-1 engines reported it clean. No sandbox malice, no dropped malicious children, and no external-intel corroboration were observed.
The file triggered three tier-1 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 75 engines flagged the sample, including three tier-1 engines. Detections are generic (PossibleThreat, ML.Attribute.HighConfidence, Trojan.Win64.Gen) with no named family agreed upon by multiple high-trust engines.
Threat Behavior
The file is unsigned. Sandbox execution showed only ambient techniques and no malicious verdict. No domains, IPs, or URLs were contacted, and the single dropped child was not flagged malicious.
What To Do Now
Do not run the file. Keep endpoint protection enabled. If the file is required, submit it to a controlled analysis environment or request additional vendor review before execution.
- 14 tier-1 engines reported clean
- no malicious sandbox verdict
- no external-intel hits
- unsigned executable
- three tier-1 detections
- medium prevalence
Treat as suspicious pending further analysis; do not execute without additional verification.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete18 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
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
- 13MITRE ATT&CK techniques
- 4spawned processes
- 0network contacts
- 5filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Used an input-capture technique that can record credentials or keystrokes.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
Note: Collects details about your system.
Note: Loads extra code modules while running.
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
ObwiessTPMSpoofer.exe
aebb6ef772be59d710d89ea46b1fafd07a8a628d9e5f494b932caa917bcc1c3b
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
cmd.exe /d /c exit 0
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\ObwiessTPMSpoofer.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
obwiess_preflight_00000AD8.tmp
C:\Users\<USER>\AppData\Local\Temp\obwiess_preflight_00000AD8.tmp
04Isolated runtime analysis - Written fileObserved
obwiess_preflight_00001B54.tmp
C:\Users\user\AppData\Local\Temp\obwiess_preflight_00001B54.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\Users\<USER>\AppData\Local\Temp\obwiess_preflight_00000AD8.tmp
- C:\Users\user\AppData\Local\Temp\obwiess_preflight_00001B54.tmp
- \Device\ConDrv\\Connect
- C:\Users\<USER>\AppData\Local\Temp\obwiess_preflight_00000AD8.tmp
- C:\Users\user\AppData\Local\Temp\obwiess_preflight_00001B54.tmp
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- fc490038819b5e0a4664…dba40aNever 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.
- 0rule hits recorded
- 18 / 75engines flagged
- 23sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
18 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 24 times from 23 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: ObwiessTPMSpoofer.exe — aebb6ef772be59d710d89ea46b1fafd07a8a628d9e5f494b932caa917bcc1c3b
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — cmd.exe /d /c exit 0
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\user\Desktop\ObwiessTPMSpoofer.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: obwiess_preflight_00000AD8.tmp — C:\Users\<USER>\AppData\Local\Temp\obwiess_preflight_00000AD8.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: obwiess_preflight_00001B54.tmp — C:\Users\user\AppData\Local\Temp\obwiess_preflight_00001B54.tmp
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
18 of 75 engines flagged this file
View all 75 engine results
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.
Fingerprint and provenance
- File name
- ObwiessTPMSpoofer.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 8.6 MB
- Last analyzed
- Aug 30, 2026, 11:33 PM UTC
aebb6ef772be59d710d89ea46b1fafd07a8a628d9e5f494b932caa917bcc1c3bSafety & 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 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?
How do I remove ObwiessTPMSpoofer.exe?
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.