Is TypingPet.exe safe?
Only APEX flagged the file, but observed LSASS targeting and process-injection, persistence, deletion, and protection-evasion techniques warrant caution despite broad engine silence.
Only 1 of 75 engines flagged this executable, and that detection came from low-trust APEX while all tier-1 engines were silent. However, the completed sandbox run mapped activity to T1055, T1485, T1547.001, and T1562.001 and reported LSASS targeting, so the file should not be trusted without publisher verification.
a89c12e65f9a06aaee…d6e1f1e45cc0a9Recommended 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.
Only 1 of 75 engines flagged this executable, and that detection came from low-trust APEX while all tier-1 engines were silent. However, the completed sandbox run mapped activity to T1055, T1485, T1547.001, and T1562.001 and reported LSASS targeting, so the file should not be trusted without publisher verification.
The antivirus result strongly resembles a false positive: APEX alone flagged the sample, while all 17 tier-1 engines reported no detection. That signal is offset by one completed sandbox run containing several offensive techniques, including process injection, persistence, data destruction, and impairment of defenses. A credential-dumping heuristic also cites interaction with LSASS, although the stored evidence does not establish a named malware family and the sandbox's overall verdict was not malicious. The signature names an unknown publisher and has neither verified status nor historical reputation, so it offers little assurance. Similar files sharing the imphash were mostly assessed cautiously, but their different signers make those matches weak because a common .NET build framework may explain the overlap. No complete contacted-host reputation check is available, though the run recorded no network contacts.
What We Detected
APEX was the only engine to flag the executable among 75 engines. All 17 tier-1 engines reported no detection, and no engine consensus identified a malware family. The file carries a signature naming “snoonqx,” but its verification status is unavailable and there is no historical signer record.
Threat Behavior
One completed sandbox run mapped activity to T1055 (process injection), T1485 (data destruction), T1547.001 (registry run keys or startup folder persistence), and T1562.001 (impair defenses). A separate heuristic cites process activity targeting LSASS, a sensitive credential store. These mappings are concerning, but the run did not receive a malicious sandbox verdict, no confirmed malicious child was found, and the stored behavior lists no persistence indicators. No complete contacted-host reputation result is available; the observed run recorded no domains, IPs, or URLs.
What To Do Now
Do not run the file on a production or personal system unless its origin and publisher can be independently verified. Keep endpoint protection enabled, obtain the program from its official release channel, and test it only in an isolated environment if further validation is necessary.
Where this verdict could be wrong3 caveats
- APEX is the only detector among 75 engines; all 17 tier-1 engines reported no detection, supporting a substantial false-positive possibility.
- behaviour.hasMaliciousSandboxVerdict=false and droppedChildren.hasMaliciousChild=false; the observed child remains unclassified rather than confirmed harmful.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false, although absent hits do not establish benignity.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1 of 75 engines flagged the sample.
- engines.tier1Malicious=0, with all 17 tier-1 engines reporting no detection.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- YARAify, CIRCL, and MalwareBazaar returned no corroborating hit.
- Runtime mapping includes T1055 process injection.
- Credential-dumping heuristic cites LSASS targeting.
- Runtime mapping includes T1562.001 impairment of defenses.
- Runtime mapping includes T1485 data destruction and T1547.001 persistence.
- Signer “snoonqx” has no established history and no confirmed verification status.
- The file was first submitted only one day ago.
Quarantine the file until its source and publisher are verified, and keep endpoint protection enabled. If execution is essential, use an isolated disposable environment rather than a normal workstation.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 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
Complete2 signature or behavior rules matched.
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
- 18MITRE ATT&CK techniques
- 12spawned processes
- 0network contacts
- 5filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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
TypingPet.exe
a89c12e65f9a06aaee03412da007e138c51234fe20a599208ad6e1f1e45cc0a9
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\TypingPet.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
TypingPet.exe.log
C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\TypingPet.exe.log
04Isolated runtime analysis - Written fileObserved
Roaming
C:\Users\user\AppData\Roaming
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\Microsoft\CLR_v4.0\UsageLogs\TypingPet.exe.log
- C:\Users\user\AppData\Roaming
- TypingPet_SingleInstance
- Global\OneSettingQueryMutex+compat+encapsulation
- \Sessions\1\BaseNamedObjects\TypingPet_SingleInstance
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- 2a02462fcbdece64775c…93bd5fNever 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.
- 2rule hits recorded
- 1 / 75engines flagged
- 17sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 75 antivirus engines flagged the file, including APEX.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 21 times from 17 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: TypingPet.exe — a89c12e65f9a06aaee03412da007e138c51234fe20a599208ad6e1f1e45cc0a9
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\TypingPet.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: TypingPet.exe.log — C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\TypingPet.exe.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Roaming — C:\Users\user\AppData\Roaming
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.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exe
1 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
A known packer signature (UPX / Themida / VMProtect / etc.) matched this file. Packers aren't malicious on their own, but most malware uses them.
Packers compress or encrypt the executable and only unpack it at runtime. Legitimate commercial software uses them too — but if the file is also unsigned and rare, it's a strong malware signal.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- TypingPet.exe
- Format
- Win32 EXE
- Code signing
- Signature not verified: snoonqx
- Size
- 166.7 KB
- Last analyzed
- Sep 25, 2026, 7:36 AM UTC
a89c12e65f9a06aaee03412da007e138c51234fe20a599208ad6e1f1e45cc0a9Safety & 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 TypingPet.exe safe, or is it malware?
What is TypingPet.exe?
How many antivirus engines detected TypingPet.exe?
What should I do if I already ran TypingPet.exe?
How do I remove TypingPet.exe?
Is TypingPet.exe digitally signed?
What is the SHA-256 hash of TypingPet.exe?
How up to date is this analysis of TypingPet.exe?
Community
Member reviews and reports for this exact file hash.