Is ABPM(F)_V5.5.5_Setup.exe safe?
Unsigned installer with direct-IP contacts and one low-trust detection but no tier-1 consensus or malicious children.
Single low-trust engine flags the file while 74 others are clean. Sandbox shows direct-IP connections without domains and two offensive MITRE techniques. No tier-1 agreement, no malicious dropped files, and rare prevalence leave the sample in mixed-signals territory.
8b660bf952fc2b40f0…110792b426a2cdRecommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer 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.
Single low-trust engine flags the file while 74 others are clean. Sandbox shows direct-IP connections without domains and two offensive MITRE techniques. No tier-1 agreement, no malicious dropped files, and rare prevalence leave the sample in mixed-signals territory.
The engine profile is dominated by a single low-trust detection with zero tier-1 malicious flags, which normally points toward false positive. However, the sandbox behaviour includes direct-IP contact to seven addresses and two MITRE techniques commonly associated with privilege escalation and persistence. The file is unsigned, rare, and carries an installer hint but lacks any corroborating malicious family or external-intel hits. These conflicting signals prevent a clean safe or malicious determination.
What We Detected
75 engines reported; only Bkav returned a malicious label (W32.AIDetectMalware). No tier-1 engine flagged the sample. The file is unsigned and shows high-entropy sections typical of packed or obfuscated code, though no packer signature was identified.
Threat Behavior
Sandbox execution revealed direct-IP connections to seven addresses and zero DNS domains, triggering the DirectIpC2 heuristic. Two offensive MITRE techniques (T1134 token manipulation, T1547.001 registry run keys) were observed alongside typical installer ambient activity. Ten dropped children were inspected; none carried malicious verdicts.
What To Do Now
Exercise caution with this rare unsigned installer. Run it in a controlled environment or obtain the file from an official vendor source if it claims to be ABPM blood-pressure monitoring software. Monitor for unexpected persistence or network activity.
Where this verdict could be wrong3 caveats
- If the direct-IP contacts are legitimate Microsoft/Cloudflare endpoints (204.79.197.203 etc.), the heuristic may be a false positive for an installer using raw IP resolution.
- Unsigned installer with high-entropy sections could be a legitimate niche medical/blood-pressure tool (ABPM acronym) rather than malware.
- No tier-1 detections, no sandbox malicious verdict, and no dropped malicious children reduce the weight of the single low-trust flag.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 74/75 engines clean
- No tier-1 malicious detections
- No malicious sandbox verdict
- No malicious dropped children
- Unsigned binary
- Direct-IP network contacts without domains
- Offensive MITRE techniques observed
- Rare prevalence (only 2 submitters)
Treat as suspicious pending further verification; do not execute on production systems without additional vetting or a trusted source.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 79 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial7 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule 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
- 17MITRE ATT&CK techniques
- 10spawned processes
- 7network contacts
- 35filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Changed an auto-start location that can make code run after sign-in or restart.
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: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
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
ABPM(F)_V5.5.5_Setup.exe
8b660bf952fc2b40f05e60f324837645cd8f9a0be177e6e198110792b426a2cd
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\ABPM_F__V5.5.5_Setup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-DQL87.tmp\ABPM_F__V5.5.5_Setup.tmp" /SL5="$5005A,22470371,119296,C:\Users\<USER>\Desktop\ABPM_F__V5.5.5_Setup.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ABPM_F__V5.5.5_Setup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-DQL87.tmp\ABPM_F__V5.5.5_Setup.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-2M8NS.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
204.79.197.203
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
52.154.209.174
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.
- 204.79.197.203
- 52.154.209.174
- 23.216.81.152
- 20.99.185.48
- 23.59.198.43
- 20.99.186.246
- 151.101.22.172
- C:\Users\<USER>\AppData\Local\Temp\is-DQL87.tmp\ABPM_F__V5.5.5_Setup.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-2M8NS.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-2M8NS.tmp\_isetup\_shfoldr.dll
- C:\Program Files (x86)\ABPM\ABPM.exe
- C:\Program Files (x86)\ABPM\DllConv.dll
- C:\Program Files (x86)\ABPM\is-R0VB4.tmp
- C:\Program Files (x86)\ABPM\is-F8R2H.tmp
- C:\Program Files (x86)\ABPM\is-FB3BS.tmp
- C:\Program Files (x86)\ABPM\is-BP8VR.tmp
- C:\Program Files (x86)\ABPM\is-RRPTS.tmp
- Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- cversions.3.m
- \Sessions\1\BaseNamedObjects\Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- \Sessions\1\BaseNamedObjects\Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- cf8a77f4cbd38f6ab44f…7adff5Never scannednever seen before
- 13f9d708533850c1348b…aadaccNever scannednever seen before
- 2e50b1f56fc0c74c255c…5a17b7Never scannednever seen before
- 7fca853e4a1cd0485402…6d3e31Never scannednever seen before
- 63595ed08fd452ea571a…a1fee0Never scannednever seen before
- 45370e81519db719413a…3c40abNever scannednever seen before
- 78755fb8c2cd1db5f344…01634dNever scannednever seen before
- 71b35dabb51f1cda0aa6…70540dNever scannednever seen before
- b6ecc658fa0b1d787afa…6da675Never scannednever seen before
- 02011fa7fa11447cd752…fbbd50Never 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.
- 1rule hit recorded
- 1 / 79engines 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 of 79 antivirus engines flagged the file, including Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 2 times from 2 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: ABPM(F)_V5.5.5_Setup.exe — 8b660bf952fc2b40f05e60f324837645cd8f9a0be177e6e198110792b426a2cd
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\ABPM_F__V5.5.5_Setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-DQL87.tmp\ABPM_F__V5.5.5_Setup.tmp" /SL5="$5005A,22470371,119296,C:\Users\<USER>\Desktop\ABPM_F__V5.5.5_Setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: ABPM_F__V5.5.5_Setup.tmp — C:\Users\<USER>\AppData\Local\Temp\is-DQL87.tmp\ABPM_F__V5.5.5_Setup.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-2M8NS.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 204.79.197.203 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 52.154.209.174 — Contact observed during runtime.
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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
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.
Evidence204.79.197.203 · 52.154.209.174 · 23.216.81.152
1 of 79 engines flagged this file
View all 79 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
Rarely uploaded, but has been around for a while. Often niche legitimate software or old internal tooling; not a strong malware signal on its own.
Fingerprint and provenance
- File name
- ABPM(F)_V5.5.5_Setup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 21.8 MB
- Last analyzed
- Jul 9, 2026, 9:57 AM UTC
8b660bf952fc2b40f05e60f324837645cd8f9a0be177e6e198110792b426a2cdSafety & 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 install 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. Download a fresh installer 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 ABPM(F)_V5.5.5_Setup.exe safe, or is it malware?
What is ABPM(F)_V5.5.5_Setup.exe?
How many antivirus engines detected ABPM(F)_V5.5.5_Setup.exe?
What should I do if I already installed ABPM(F)_V5.5.5_Setup.exe?
How do I remove ABPM(F)_V5.5.5_Setup.exe?
What is the SHA-256 hash of ABPM(F)_V5.5.5_Setup.exe?
How up to date is this analysis of ABPM(F)_V5.5.5_Setup.exe?
Community
Member reviews and reports for this exact file hash.