Is HRKill.exe safe?
Suspicious file assessment
1 high-confidence signature or behavior rule matched this file.
d7212aa08e8b02523f…a4ec4eed174edcRecommended 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.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
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
- 19MITRE ATT&CK techniques
- 8spawned processes
- 1network contacts
- 18filesystem & 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: Created or modified a system service, which can keep code running.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
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.
Moderate concern: Checked the environment for virtualisation or analysis tools.
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
HRKill.exe
d7212aa08e8b02523f616b5890ce3b36fa0b175ce610ba43eca4ec4eed174edc
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\software.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\BF87.tmp" 688
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
BF87.tmp
C:\Users\<USER>\AppData\Local\Temp\BF87.tmp
04Isolated runtime analysis - Written fileObserved
3PMQFOOk.sys
C:\Windows\sysnative\drivers\3PMQFOOk.sys
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\BF87.tmp
- C:\Windows\sysnative\drivers\3PMQFOOk.sys
- C:\Users\<USER>\AppData\Local\Temp\D0CE.tmp
- C:\Users\<USER>\AppData\Local\Temp\E0FB.tmp
- C:\Windows\System32\drivers\dgZBNTjlSM.sys
- C:\Users\<USER>\AppData\Local\Temp\E0FB.tmp
- C:\Users\user\AppData\Local\Temp\206F.tmp
- C:\Users\user\AppData\Local\Temp\BC93.tmp
- C:\Windows\System32\drivers\5vz_Sv1qdyfY3K.sys
- C:\Windows\System32\drivers\UYAjTEAZmNf1Ml.sys
- HRKILLUI
- \Sessions\1\BaseNamedObjects\HRKILLUI
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- 114b0d6799ec2563969c…cd4e5cNever scannednever seen before
- 6272e419c24523f3e0a1…b556d5Never scannednever seen before
- d3bd429836092aa05c3d…473796Never scannednever seen before
- 23b8be7673546c504142…e072c1Never 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
- 4 / 75engines flagged
- 2sources 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
4 of 75 antivirus engines flagged the file, including Bkav and Cylance.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from 北京火绒网络科技有限公司.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: HRKill.exe — d7212aa08e8b02523f616b5890ce3b36fa0b175ce610ba43eca4ec4eed174edc
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\BF87.tmp" 688
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: BF87.tmp — C:\Users\<USER>\AppData\Local\Temp\BF87.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 3PMQFOOk.sys — C:\Windows\sysnative\drivers\3PMQFOOk.sys
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: pua
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 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.
Evidence162.159.36.2Packed PE with sandbox-observed network activity AND engine flags. Signed packed software exists legitimately, but a signed + packed + flagged binary is a signed dropper pattern.
Evidence162.159.36.2
4 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. 4 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- HRKill.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: 北京火绒网络科技有限公司
- Size
- 1.9 MB
- Last analyzed
- May 19, 2026, 5:34 PM UTC
d7212aa08e8b02523f616b5890ce3b36fa0b175ce610ba43eca4ec4eed174edcSafety & 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 HRKill.exe safe, or is it malware?
What is HRKill.exe?
How many antivirus engines detected HRKill.exe?
What should I do if I already ran HRKill.exe?
How do I remove HRKill.exe?
What kind of malware is HRKill.exe?
Is HRKill.exe digitally signed?
What is the SHA-256 hash of HRKill.exe?
How up to date is this analysis of HRKill.exe?
Community
Member reviews and reports for this exact file hash.