Is bitrecover-vcard-viewer.exe safe?
Low-trust detections, unsigned publisher, and mixed imphash history leave the file in mixed-signals territory.
Two low-tier engines flagged the sample while 17 tier-1 engines stayed silent. The signer has no history, the file shows process-injection and persistence techniques, and similar imphash matches produced conflicting verdicts. No tier-1 family consensus or malicious child files were found.
f01301bac01136c4f8…1791f64cc20ce3Recommended 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-tier engines flagged the sample while 17 tier-1 engines stayed silent. The signer has no history, the file shows process-injection and persistence techniques, and similar imphash matches produced conflicting verdicts. No tier-1 family consensus or malicious child files were found.
The detection pattern is classic low-signal: only two non-tier-1 engines reported, one labeling grayware and the other an ML score. The publisher Tweakomatic Ltd. has no prior samples in our records, removing the usual signed-installer safety net. Runtime evidence shows four offensive MITRE techniques, yet the single sandbox run returned no malicious verdict. Similar imphash files range from safe to malicious, indicating framework collisions rather than a reliable family match. With medium prevalence and no external-intel hits, the evidence remains inconclusive.
What We Detected
2 of 76 engines flagged the file: CrowdStrike labeled it grayware at 60 % confidence and Trapmine returned a low-trust ML suspicion score. No tier-1 engine raised an alert, and no named malware family achieved consensus.
Threat Behavior
The sample exhibits process injection (T1055), token manipulation (T1134), persistence via startup folder (T1547.001), and defense-evasion (T1562.001). It wrote multiple temporary installer files and contacted six external IP addresses without domain names. No malicious dropped children were identified.
What To Do Now
Keep endpoint protection enabled. If the file is not required, delete it and re-download from the vendor site. Monitor for unexpected outbound connections to the observed IPs.
Where this verdict could be wrong1 caveat
- contactedHosts=null — host-reputation cross-check incomplete; cannot confirm clean network behaviour.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero tier-1 malicious detections
- No malicious dropped children
- Medium prevalence over 3603 days
- Unsigned or unverified publisher with no history
- Four offensive MITRE techniques observed
- Direct-IP network traffic without domain names
- Mixed verdicts on similar imphash files
Treat the file as suspicious; do not run it without additional verification or sandboxing.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial7 runtime contacts were 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
- 21MITRE ATT&CK techniques
- 7spawned processes
- 7network contacts
- 38filesystem & 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.
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.
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
bitrecover-vcard-viewer.exe
f01301bac01136c4f878345ac33a90fc42c77111325157c9071791f64cc20ce3
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-A49C1.tmp\file.tmp" /SL5="$20174,2943489,254976,C:\Users\<USER>\Desktop\file.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
file.tmp
C:\Users\<USER>\AppData\Local\Temp\is-A49C1.tmp\file.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-5SDGT.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
20.99.133.109
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
a83f:8110:2800:0:2800:0:1800:0
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.
- 20.99.133.109
- a83f:8110:2800:0:2800:0:1800:0
- 192.168.0.19
- 20.99.186.246
- 23.216.81.152
- 184.25.191.235
- <MACHINE_DNS_SERVER>
- C:\Users\<USER>\AppData\Local\Temp\is-A49C1.tmp\file.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-5SDGT.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-5SDGT.tmp\_isetup\_shfoldr.dll
- C:\Users\<USER>\AppData\Local\Temp\is-5SDGT.tmp\isxdl.dll
- C:\Documents and Settings\Administrator\Local Settings\Temp\is-TDHA9.tmp\996E.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERFF9.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER10C4.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER10F4.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER11EE.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER11FE.tmp.csv
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.TMD.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- b0cc4697b2fd1b4163fd…b685b3Never scannednever seen before
- 9884e9d1b4f8a873ccbd…360d87Never scannednever seen before
- 38fccac2d35535d00647…e41587Never scannednever seen before
- a4c86fc4836ac728d7bd…95fd81Never scannednever seen before
- d582d5f69b13b6861a6b…2c28ebNever scannednever seen before
- 17b437c88a32518d03eb…8e9de9Never scannednever seen before
- 0ec20fd5e3b069d16a1e…722070Never scannednever seen before
- 115c86cb746fb08069a4…326a1dNever scannednever seen before
- 8142b717b7ac30e694fb…1d5a7bNever scannednever seen before
- 4442a9d64fb3d6780ac7…320debNever 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
- 2 / 76engines flagged
- 36sources 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
2 of 76 antivirus engines flagged the file, including CrowdStrike and Trapmine.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 38 times from 36 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: bitrecover-vcard-viewer.exe — f01301bac01136c4f878345ac33a90fc42c77111325157c9071791f64cc20ce3
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-A49C1.tmp\file.tmp" /SL5="$20174,2943489,254976,C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: file.tmp — C:\Users\<USER>\AppData\Local\Temp\is-A49C1.tmp\file.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-5SDGT.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 20.99.133.109 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: a83f:8110:2800:0:2800:0:1800:0 — 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
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.
Evidence"C:\Users\<USER>\Desktop\file.exe"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.
Evidence20.99.133.109 · a83f:8110:2800:0:2800:0:1800:0 · 20.99.186.246
2 of 76 engines flagged this file
View all 76 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
- bitrecover-vcard-viewer.exe
- Format
- Win32 EXE
- Code signing
- Signature not verified: Tweakomatic Ltd.
- Size
- 3.2 MB
- Last analyzed
- Aug 21, 2026, 6:41 PM UTC
f01301bac01136c4f878345ac33a90fc42c77111325157c9071791f64cc20ce3Safety & 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 bitrecover-vcard-viewer.exe safe, or is it malware?
What is bitrecover-vcard-viewer.exe?
How many antivirus engines detected bitrecover-vcard-viewer.exe?
What should I do if I already ran bitrecover-vcard-viewer.exe?
How do I remove bitrecover-vcard-viewer.exe?
Is bitrecover-vcard-viewer.exe digitally signed?
What is the SHA-256 hash of bitrecover-vcard-viewer.exe?
How up to date is this analysis of bitrecover-vcard-viewer.exe?
Community
Member reviews and reports for this exact file hash.