Is Hinaware_Feet.exe safe?
Unsigned 40 MB PE with 2 low-trust detections, 8 YARAify rules, and T1486 encryption technique.
Two low-trust engines flagged the file while 63 others did not; YARAify matched 8 researcher rules and the sample performed direct-IP connections plus data-encryption behaviour. No tier-1 consensus or signed-publisher history exists, leaving mixed signals.
fa63c1263773d9ef16…f7b85a35290497Recommended 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.
Two low-trust engines flagged the file while 63 others did not; YARAify matched 8 researcher rules and the sample performed direct-IP connections plus data-encryption behaviour. No tier-1 consensus or signed-publisher history exists, leaving mixed signals.
The engine profile shows only low-trust detections and no tier-1 family consensus, which normally leans safe, but the unsigned status, eight YARAify rule hits, and T1486 technique plus direct-IP traffic create a counter-signal. Medium prevalence and absence of prior similar-hash verdicts prevent a confident clean call. The combination of static and behavioural indicators therefore places the file in the suspicious band.
What We Detected
Two low-trust engines (APEX, Bkav) reported malicious while 63 others returned clean; no tier-1 engine raised an alert. Eight YARAify community rules matched, including debugger checks and Python-AI library dependencies. The sample is unsigned and 40 MB in size.
Threat Behavior
Runtime traces show T1486 data-encryption activity and seven direct-IP connections without domain resolution. Ten dropped children were inspected and none carried malicious verdicts. No sandbox returned a malicious verdict.
What To Do Now
Keep endpoint protection enabled. Do not execute the file on production systems. Submit the sample to a sandbox service for deeper behavioural logging and monitor any follow-up community analysis.
Where this verdict could be wrong1 caveat
- communityComments[0] labels the file clean (0/100) on threat.rip — single researcher annotation with no votes.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- tier1Malicious=0
- onlyLowTrustFlagging=true
- no malicious dropped children
- unsigned executable
- T1486 data-encryption technique observed
- direct-IP C2 traffic without domain resolution
- 8 YARAify community rules matched
Treat the file as suspicious; do not run it until additional sandbox or researcher analysis confirms its intent.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial7 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete6 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
- 15MITRE ATT&CK techniques
- 7spawned processes
- 7network contacts
- 17filesystem & 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.
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
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
Hinaware_Feet.exe
fa63c1263773d9ef16ce1164ec279e70f072b5c776a4b40104f7b85a35290497
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Hinaware_Feet.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\Hinaware_Feet.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
_imaging.cp313-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI61682\PIL\_imaging.cp313-win_amd64.pyd
04Isolated runtime analysis - Written fileObserved
_imagingcms.cp313-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI61682\PIL\_imagingcms.cp313-win_amd64.pyd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
23.55.140.42
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
151.101.22.172
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 23.55.140.42
- 151.101.22.172
- 184.27.218.92
- 20.69.140.28
- 23.196.145.221
- 104.98.118.176
- 20.99.133.109
- C:\Users\<USER>\AppData\Local\Temp\_MEI61682\PIL\_imaging.cp313-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI61682\PIL\_imagingcms.cp313-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI61682\PIL\_imagingmath.cp313-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI61682\PIL\_imagingtk.cp313-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI61682\PIL\_webp.cp313-win_amd64.pyd
- %USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes\TranscodedWallpaper
- %USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes\CachedFiles\CachedImage_1280_1024_POS4.jpg
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 48f4a239c25354f0e9f8…17ecedNever scannednever seen before
- 3271d39d7b4dcd841e8e…efe5e5Never scannednever seen before
- cb71909bf01a3a7a4c73…d46e13Never scannednever seen before
- 6a99bc0128e0c7d6cbbf…cbc6c8Never scannednever seen before
- 98074c85650a420a095a…b084e9Never scannednever seen before
- 81eca6840b87f2def9fc…d7aaaaNever scannednever seen before
- 4f05f31ca026bbfeeee4…7ab5deNever scannednever seen before
- 5c0d5082fba1a2a3eb8d…198815Never scannednever seen before
- 3130bf26da0c840c1e02…5a3539Never scannednever seen before
- 47576cae321c80e69c7f…ac6b91Never 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.
- 6rule hits recorded
- 2 / 75engines flagged
- 46sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
5 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceObservedSourceSignature and behavior rulesObserved at - 02
2 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
YARAify matched 8 researcher rules to this file.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Hinaware_Feet.exe — fa63c1263773d9ef16ce1164ec279e70f072b5c776a4b40104f7b85a35290497
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\Hinaware_Feet.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\Hinaware_Feet.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _imaging.cp313-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI61682\PIL\_imaging.cp313-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _imagingcms.cp313-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI61682\PIL\_imagingcms.cp313-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 23.55.140.42 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 151.101.22.172 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched 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.
- DebuggerCheck__API
- DebuggerException__SetConsoleCtrl
- dependsonpythonailib
- golang_bin_JCorn_CSC846
- maldoc_indirect_function_call_3
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence23.55.140.42 · 151.101.22.172 · 184.27.218.92
2 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
- Hinaware_Feet.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 38.6 MB
- Last analyzed
- Aug 14, 2026, 2:56 AM UTC
fa63c1263773d9ef16ce1164ec279e70f072b5c776a4b40104f7b85a35290497Safety & 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 Hinaware_Feet.exe safe, or is it malware?
What is Hinaware_Feet.exe?
How many antivirus engines detected Hinaware_Feet.exe?
What should I do if I already ran Hinaware_Feet.exe?
How do I remove Hinaware_Feet.exe?
What is the SHA-256 hash of Hinaware_Feet.exe?
How up to date is this analysis of Hinaware_Feet.exe?
Community
Member reviews and reports for this exact file hash.