Is allwaysync-x64-21-1-5.exe safe?
No antivirus engine detected this established, Botkind-signed Allway Sync installer, while the behavioral warnings remain uncorroborated by sandbox, child-file, or network reputation findings.
All 74 antivirus engines returned no detection, including 17 tier-1 engines, and the executable carries a verified Botkind signature. One sandbox produced aggressive behavioral mappings involving process injection and credential access, but its overall result, inspected child files, and fully covered domain-reputation check did not corroborate malware activity.
41581a1f85f246434f…5ff0d46589d9aaRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
All 74 antivirus engines returned no detection, including 17 tier-1 engines, and the executable carries a verified Botkind signature. One sandbox produced aggressive behavioral mappings involving process injection and credential access, but its overall result, inspected child files, and fully covered domain-reputation check did not corroborate malware activity.
The strongest evidence is broad antivirus agreement: none of 74 engines detected a threat, including 17 tier-1 products. The executable is signed with a verified Botkind certificate and has been submitted 309 times by 233 sources since 2021. Its completed sandbox run installed Allway Sync components and a named synchronization service without producing a malicious sandbox verdict. Behavioral heuristics mapped activity to process injection, LSASS access, persistence, and other offensive techniques, so those findings should not be ignored. However, all 10 inspected child files avoided a malicious result, and the reputation check covered all six contacted domains without identifying a malicious or suspicious host. The mixed prior imphash results involve different signers and are weak identity matches rather than reliable evidence about this executable.
What We Detected
None of 74 antivirus engines flagged the executable, and all 17 reporting tier-1 engines returned no detection. The file has a verified signature from Botkind, no detected brand mismatch, and an established submission history dating to 2021.
Threat Behavior
One completed sandbox run installed Allway Sync through Windows Installer and created BotkindSyncService. Behavioral heuristics mapped some activity to T1055 process injection, credential-store access, persistence, and defense evasion; these are meaningful warnings, but the sandbox itself produced no malicious verdict. Ten inspected child files yielded no malicious child, and reputation coverage for all six contacted domains found no known malicious or suspicious host.
What To Do Now
Use the installer only if it came from the official Allway Sync distribution channel and its Botkind signature remains valid. Keep endpoint protection enabled, and avoid running the file if its source or signature differs from the evidence summarized here.
Where this verdict could be wrong4 caveats
- triggeredHeuristics includes MalwareTips.Synth.ProcessInjection tied to T1055 and a credential-access warning involving lsass.exe; these are significant behavioral counter-signals despite lacking independent corroboration.
- behaviour.offensiveCount=8 includes T1562.001, T1485, and T1547.001, although the single completed sandbox assigned no malicious verdict.
- signing.signerStats.found=false, so the verified 'Botkind' signature has no established internal signer history.
- similarHashes shows one malicious and two suspicious prior verdicts for imphash 5a594319a0d69dbc452e748bcf05892e, but every match has signerMatchesSubject=false.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/74 antivirus engines detected a threat.
- All 17 reporting tier-1 engines returned no detection.
- The Botkind digital signature is verified.
- The file has 309 submissions from 233 sources since 2021.
- No malicious child or contacted domain was identified under complete listed-domain coverage.
- Behavioral mapping includes T1055 process injection.
- A heuristic reported access involving lsass.exe.
- Eight offensive MITRE techniques were associated with the sandbox trace.
- The Botkind signer has no stored historical sample statistics.
- Service-based persistence was observed through BotkindSyncService.
Obtain the installer from the official vendor channel and verify that Windows still reports a valid Botkind signature before use. Keep antivirus and endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial6 of 26 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete3 signature or behavior rules matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 37MITRE ATT&CK techniques
- 15spawned processes
- 26network contacts
- 40filesystem & mutex artifacts
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.
- www.microsoft.com
- res.public.onecdn.static.microsoft
- fp2e7a.wpc.phicdn.net
- fp2e7a.wpc.2be4.phicdn.net
- svc.ha-teams.office.com
- svc.ms-acdc-teams.office.com
- 13.107.4.50
- 23.216.147.76
- 104.86.182.43
- 23.216.147.64
- a83f:8110:0:0:9800:0:0:0
- 131.253.33.203
- a83f:8110:0:0:678a:21:0:0
- 20.99.132.105
- 20.80.129.13
- 20.99.133.109
- BotkindSyncService
- HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\EventLog\Application\BotkindSyncService\EventMessageFile
- HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\EventLog\Application\BotkindSyncService\TypesSupported
- HKEY_CURRENT_USER\SOFTWARE\SyncApp\l4B5F4749464E4F436554534E495F5945
- HKEY_CURRENT_USER\SOFTWARE\SyncApp\4B5F4749464E4F436554534E495F5945
- HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{6232211d-bf20-eec9-31fb-ff90e69218c7}\l4B5F4749464E4F436554534E495F5945
- HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{6232211d-bf20-eec9-31fb-ff90e69218c7}\4B5F4749464E4F436554534E495F5945
- C:\Users\<USER>\AppData\Local\Temp\is-0DN64.tmp\file.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-9MC70.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-9MC70.tmp\is-PATSD.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-9MC70.tmp\allwaysync-x64-21-1-5.msi
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
- C:\Users\<USER>\AppData\Local\Temp\is-9MC70.tmp\allwaysync-x64-21-1-5.msi
- C:\Users\<USER>\AppData\Local\Temp\is-9MC70.tmp\_isetup
- C:\Config.Msi\CMP2872.tmp
- C:\Config.Msi
- C:\Windows\Installer\112da.msi
- Global\_MSIExecute
- Global\__BotkindSyncServiceM
- Global\SyncAppMutex
- Bruno_SyncAppMutex
- Local\MSIMGSIZECacheMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- e451bc0c9d68c7b8737a…4876eeNever scannednever seen before
- cb1a5a7a5765ee276e60…75e994Never scannednever seen before
- 5d90da54f37dd608034f…432d4dNever scannednever seen before
- e33e1924c8fa87dd5977…e9b6e9Never scannednever seen before
- 0932ee61b842b8a16b0b…cae85aNever scannednever seen before
- 3881485249497377c497…fe9135Never scannednever seen before
- adbeb62bc45164656fbc…19f0e8Never scannednever seen before
- d80ff77ee9854c98f0f5…4b75d6Never scannednever seen before
- cc57a461315ea800dd1d…d0b6b5Never scannednever seen before
- febdab4af0f565c24a07…a170d2Never 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.
- 3rule hits recorded
- 0 / 74engines flagged
- 233sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 233 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 04
Scanned file: allwaysync-x64-21-1-5.exe — 41581a1f85f246434fc922fa0f2f13dec06a81454ea2d1c9a95ff0d46589d9aa
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-0DN64.tmp\file.tmp" /SL5="$20174,11600471,780288,C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: file.tmp — C:\Users\<USER>\AppData\Local\Temp\is-0DN64.tmp\file.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-9MC70.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 10
Contacted host: res.public.onecdn.static.microsoft — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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.
Sandbox flagged persistence indicators (registry Run keys / services / scheduled tasks).
EvidenceBotkindSyncServiceThe 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
0 of 74 engines flagged this file
View all 74 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- allwaysync-x64-21-1-5.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Botkind
- Size
- 11.9 MB
- Last analyzed
- Oct 4, 2026, 4:17 AM UTC
41581a1f85f246434fc922fa0f2f13dec06a81454ea2d1c9a95ff0d46589d9aaSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is allwaysync-x64-21-1-5.exe safe?
What is allwaysync-x64-21-1-5.exe?
How many antivirus engines detected allwaysync-x64-21-1-5.exe?
Is allwaysync-x64-21-1-5.exe digitally signed?
What is the SHA-256 hash of allwaysync-x64-21-1-5.exe?
Is it safe to run allwaysync-x64-21-1-5.exe?
How up to date is this analysis of allwaysync-x64-21-1-5.exe?
Community
Member reviews and reports for this exact file hash.