You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for reporting this, and for including the hash.
The MD5 in your ANY.RUN screenshot (B8EC2BD8B8B48FEF652EB93702533F0F) is the official PhoneBoxAgent-0.9.6-win-x64.zip from the 0.9.6 release, built from this repository by GitHub Actions. You can check any download yourself:
sha256sum PhoneBoxAgent-0.9.6-win-x64.zip # compare with SHA256SUMS-0.9.6.txt in the release
gh attestation verify PhoneBoxAgent-0.9.6-win-x64.zip --repo ersinkoc/phonebox # build provenance
Trojan:Script/Wacatac.H!ml is a generic machine-learning verdict (the !ml suffix) that Defender gives to new, unsigned programs that do things like start other programs. PhoneBox does that by design: the agent runs the shortcuts and commands you configure, and the details text ("executes commands") describes exactly that. A local Defender scan with today's signatures finds nothing in the same file, so the verdict comes from the cloud reputation check on downloads. ANY.RUN's "malicious activity" label for the agent comes from the same kind of behaviour (starting processes, listening on a local port).
What we're doing about it:
Submitting the release files to Microsoft as a false positive.
Hi, I'm using PhoneBox 0.9.10 on Windows 11 x64 (build 26200).
I performed a clean reinstall using the official setup script. The release ZIP checksum verified successfully, but launching the agent fails with:
Setup stopped: This command cannot be run due to the error: An Application Control policy has blocked this file.
Get-AuthenticodeSignature reports NotSigned for PhoneBoxAgent.exe.
Smart App Control is enabled, and I would prefer to keep it enabled.
Could you please provide an update on SignPath approval and the expected availability of a signed Windows release? Is there any supported installation method compatible with SAC enforcement?
Thanks for the clear report. And yes, please keep Smart App Control on.
Signing status: the SignPath Foundation application was submitted on 2026-11-15 and is under review (#56). I don't have a date: it depends on their review. Once it's approved, releases will ship a signed PhoneBoxAgent.exe, and I'll post here and in #56.
Running with Smart App Control on: there is no supported way today. Smart App Control has no per-app exception list. It allows a program only when it is signed or has enough cloud reputation, and a new unsigned release has neither. The signed release is the real fix, so I won't suggest workarounds that would weaken it.
Setup: you shouldn't have seen "Setup stopped" for this. #101 changes setup.ps1:
it recognizes this block, says PhoneBox is installed but can't run until it is signed, and finishes normally;
its earlier warning no longer claims the release agent runs with Smart App Control on, which your report shows it doesn't.
The files setup installed are fine. Once a signed release is out, run setup again to get it; the agent will then start.
0.9.11 includes the setup change (#101). With Smart App Control on, setup now finishes and explains the block instead of stopping. The agent is still unsigned until the SignPath review (#56) is done, so Smart App Control will keep blocking it until then. I'll post here when a signed release is available.
Activity
ersinkoc commentedon Nov 15, 2026
Thanks for reporting this, and for including the hash.
The MD5 in your ANY.RUN screenshot (
B8EC2BD8B8B48FEF652EB93702533F0F) is the officialPhoneBoxAgent-0.9.6-win-x64.zipfrom the 0.9.6 release, built from this repository by GitHub Actions. You can check any download yourself:Trojan:Script/Wacatac.H!mlis a generic machine-learning verdict (the!mlsuffix) that Defender gives to new, unsigned programs that do things like start other programs. PhoneBox does that by design: the agent runs the shortcuts and commands you configure, and the details text ("executes commands") describes exactly that. A local Defender scan with today's signatures finds nothing in the same file, so the verdict comes from the cloud reputation check on downloads. ANY.RUN's "malicious activity" label for the agent comes from the same kind of behaviour (starting processes, listening on a local port).What we're doing about it:
PhoneBoxAgent.exe. If Defender flags that one too, please tell me here.If you'd rather not run a prebuilt binary, the agent also builds from source with
scripts/install.ps1(see the README's quick start).Vishwas-27 commentedon Nov 16, 2026
Hi, I'm using PhoneBox 0.9.10 on Windows 11 x64 (build 26200).
I performed a clean reinstall using the official setup script. The release ZIP checksum verified successfully, but launching the agent fails with:
Setup stopped: This command cannot be run due to the error: An Application Control policy has blocked this file.Get-AuthenticodeSignaturereportsNotSignedfor PhoneBoxAgent.exe.Smart App Control is enabled, and I would prefer to keep it enabled.
Could you please provide an update on SignPath approval and the expected availability of a signed Windows release? Is there any supported installation method compatible with SAC enforcement?
Thanks!
ersinkoc commentedon Nov 16, 2026
Thanks for the clear report. And yes, please keep Smart App Control on.
Signing status: the SignPath Foundation application was submitted on 2026-11-15 and is under review (#56). I don't have a date: it depends on their review. Once it's approved, releases will ship a signed
PhoneBoxAgent.exe, and I'll post here and in #56.Running with Smart App Control on: there is no supported way today. Smart App Control has no per-app exception list. It allows a program only when it is signed or has enough cloud reputation, and a new unsigned release has neither. The signed release is the real fix, so I won't suggest workarounds that would weaken it.
Setup: you shouldn't have seen "Setup stopped" for this. #101 changes
setup.ps1:The files setup installed are fine. Once a signed release is out, run setup again to get it; the agent will then start.
setup.ps1: explain a Smart App Control block instead of stopping (#69) (
Release 0.9.11: Android 7+, raw-input shortcut keys, Terminal and set…
ersinkoc commentedon Nov 16, 2026
0.9.11 includes the setup change (#101). With Smart App Control on, setup now finishes and explains the block instead of stopping. The agent is still unsigned until the SignPath review (#56) is done, so Smart App Control will keep blocking it until then. I'll post here when a signed release is available.