Repository navigation
Releases
Zero Breach Toolkit 3.0.2
Zero Breach Toolkit 3.0.2.
3.0.2 fixes what the first testers found. The window fits small laptop screens; on a Mac a folder that waits for permission no longer holds the check; the household report is saved privately and practice examples are labelled as such; a message with no link now warns never to share a login code; and more. If you have 3.0.0 or 3.0.1, use this one. Full list in the CHANGELOG.
More than a spyware check. Version 3 still looks for known spyware, and now also shows the ways in that are left open on your devices and how to close them, checks the links, emails, files and QR codes people send you, and walks you through your accounts, your home network and the trackers and hidden networks around you. Everything runs on your own computer, and nothing leaves it unless you say yes.
Download the file for your computer
| Your computer | Download | The first time you open it |
|---|---|---|
| Windows | zero-breach-toolkit-windows-x64.exe |
Windows may say it "protected your PC". Click More info, then Run anyway. |
| Mac with Apple silicon (M1 or newer) | zero-breach-toolkit-macos-apple-silicon.dmg |
Drag Zero Breach Toolkit to Applications and open it. macOS stops it once: open System Settings → Privacy & Security, click Open Anyway, and open it again. |
| Mac with Intel | zero-breach-toolkit-macos-intel.dmg |
As above. |
| Linux | zero-breach-toolkit-linux-x64.tar.gz |
Extract it and run ./zero-breach-toolkit (add --gui for the window). |
| Any computer with Python | zero-breach-toolkit.py |
The same check in one readable file, for people who want to see exactly what runs. |
The warnings appear because the programs are not yet signed by Microsoft or Apple. Code signing is on its way: the project has been accepted by the SignPath Foundation and the certificate is being issued. Until then, each program is built by GitHub from this release's published source, with a public build record you can check before running it (see Verify below).
What's new
- Doors to close. Every check now lists the ways in that are left open - Remote Desktop, automatic sign-in, no disk encryption, Secure Boot off, browser extensions that can read every site, no ad blocker, an iPhone without a passcode, old Android security updates - each with why it matters and how to close it. "Close the doors found open" can switch some of them off for you, one at a time, after asking, with a way back.
- Check what you were sent. Paste a text, WhatsApp or Signal message or a link; open a saved email; choose a suspicious file or a picture of a QR code. The toolkit says what it really is and whether it matches known spyware or common tricks, without opening, running or following anything. A file can also be looked up online, only if you say yes.
- Was my phone copied? For a phone that was taken from you, for example at a border: signs that it was plugged into a phone-forensics tool such as Cellebrite. Finding nothing is not proof, and the report says so.
- Check your online accounts. A guided list of where to look - devices linked to WhatsApp, Signal, Telegram, Apple, Google and Microsoft, email forwarding, location sharing, a lock on your phone number - starting with the single best thing you can do: sign in with a physical security key. Your answers are kept until you finish.
- Your home and what is around you. Who is on your Wi-Fi and which doors their devices leave open (it asks first); hidden Wi-Fi networks nearby, what each one probably is, and on Windows and Linux a meter that follows one network's signal so you can find the device; Bluetooth trackers such as AirTags that stay near you.
- Look closer at a computer. What starts automatically, explained entry by entry; Windows' own records of hidden commands, downloads that were run and protection switched off; a network recording from a phone, with which company runs each address contacted.
- Live connections, explained. A "Who runs it" column (Google, Microsoft, Cloudflare, Meta, Apple, Amazon and more, from a list built into the program) and a right-click for the program behind each connection, when it started and what started it.
- One report for the household. Put the saved results of every computer, phone and check on one page, worst first, with a list of what has not been checked yet.
- Plain words first. Every result opens with a few lines in plain words: what was found, what it means, what to do. "Not sure where to start?" asks what happened and opens the right check. One button sends the result to someone who can help.
- Every tool in 27 languages. The results of all the smaller tools are now translated too, not only their buttons. Saved results stay in English, the record a helpline works from.
- A friendlier terminal. Choose from the menu with the arrow keys (or type the number), with one progress line and the result in colour.
- More spyware and more programs recognised. 14 mercenary spyware indicator lists built in so they work offline, 9,014 malicious browser extensions, 2,211 vulnerable or malicious drivers, 200+ remote-access programs, and better reading of iPhone backups from iOS 27.
Fixes since 2.0.7
- A "worth a look" result no longer looks like a clean one, and Windows' own built-in event-log subscription is no longer reported as an attack.
- iPhone backups from iOS 27: installed apps, newer diagnostic reports and large Shortcuts are read again (reported by Natha, #47).
- The doors tool and the report now agree on how many doors are open.
- Saving over an existing file, a damaged picture and an empty option now give a clear message instead of an error.
Thank you to everyone who reported problems and tested on real machines, especially Natha, Verchiel666 and dhruv1220.
Full list in CHANGELOG.md.
Verify before running
zero-breach-toolkit.py SHA-256: 0b6df5f02c6b13256b735bfb55c1ef0a31ff0c762550910be9f66b4f5090dafb
Each program: gh attestation verify <file> --repo interplains/Zero-Breach-Toolkit.
Checksums and signatures: import the signing key from this release's files first, then verify.
gpg --import archivegenocide-signing-key.asc
gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt
Signed with key C24E C92B 12D6 670A 2516 065F 9B4D 5754 99AF A53C. "This key is not certified with a trusted signature" is normal: it only means you have not signed the key yourself. See docs/VERIFYING.md.
Zero Breach Toolkit 3.0.1
Superseded by v3.0.2: https://github.com/interplains/Zero-Breach-Toolkit/releases/tag/v3.0.2
Zero Breach Toolkit 3.0.1.
3.0.1 follows 3.0.0 within the hour: the result card now names what was found, and "Show full report" opens in its own window, so both work on small screens. If you downloaded 3.0.0, use this one.
More than a spyware check. Version 3 still looks for known spyware, and now also shows the ways in that are left open on your devices and how to close them, checks the links, emails, files and QR codes people send you, and walks you through your accounts, your home network and the trackers and hidden networks around you. Everything runs on your own computer, and nothing leaves it unless you say yes.
Download the file for your computer
| Your computer | Download | The first time you open it |
|---|---|---|
| Windows | zero-breach-toolkit-windows-x64.exe |
Windows may say it "protected your PC". Click More info, then Run anyway. |
| Mac with Apple silicon (M1 or newer) | zero-breach-toolkit-macos-apple-silicon.dmg |
Drag Zero Breach Toolkit to Applications and open it. macOS stops it once: open System Settings → Privacy & Security, click Open Anyway, and open it again. |
| Mac with Intel | zero-breach-toolkit-macos-intel.dmg |
As above. |
| Linux | zero-breach-toolkit-linux-x64.tar.gz |
Extract it and run ./zero-breach-toolkit (add --gui for the window). |
| Any computer with Python | zero-breach-toolkit.py |
The same check in one readable file, for people who want to see exactly what runs. |
The warnings appear because the programs are not yet signed by Microsoft or Apple. Code signing is on its way: the project has been accepted by the SignPath Foundation and the certificate is being issued. Until then, each program is built by GitHub from this release's published source, with a public build record you can check before running it (see Verify below).
What's new
- Doors to close. Every check now lists the ways in that are left open - Remote Desktop, automatic sign-in, no disk encryption, Secure Boot off, browser extensions that can read every site, no ad blocker, an iPhone without a passcode, old Android security updates - each with why it matters and how to close it. "Close the doors found open" can switch some of them off for you, one at a time, after asking, with a way back.
- Check what you were sent. Paste a text, WhatsApp or Signal message or a link; open a saved email; choose a suspicious file or a picture of a QR code. The toolkit says what it really is and whether it matches known spyware or common tricks, without opening, running or following anything. A file can also be looked up online, only if you say yes.
- Was my phone copied? For a phone that was taken from you, for example at a border: signs that it was plugged into a phone-forensics tool such as Cellebrite. Finding nothing is not proof, and the report says so.
- Check your online accounts. A guided list of where to look - devices linked to WhatsApp, Signal, Telegram, Apple, Google and Microsoft, email forwarding, location sharing, a lock on your phone number - starting with the single best thing you can do: sign in with a physical security key. Your answers are kept until you finish.
- Your home and what is around you. Who is on your Wi-Fi and which doors their devices leave open (it asks first); hidden Wi-Fi networks nearby, what each one probably is, and on Windows and Linux a meter that follows one network's signal so you can find the device; Bluetooth trackers such as AirTags that stay near you.
- Look closer at a computer. What starts automatically, explained entry by entry; Windows' own records of hidden commands, downloads that were run and protection switched off; a network recording from a phone, with which company runs each address contacted.
- Live connections, explained. A "Who runs it" column (Google, Microsoft, Cloudflare, Meta, Apple, Amazon and more, from a list built into the program) and a right-click for the program behind each connection, when it started and what started it.
- One report for the household. Put the saved results of every computer, phone and check on one page, worst first, with a list of what has not been checked yet.
- Plain words first. Every result opens with a few lines in plain words: what was found, what it means, what to do. "Not sure where to start?" asks what happened and opens the right check. One button sends the result to someone who can help.
- Every tool in 27 languages. The results of all the smaller tools are now translated too, not only their buttons. Saved results stay in English, the record a helpline works from.
- A friendlier terminal. Choose from the menu with the arrow keys (or type the number), with one progress line and the result in colour.
- More spyware and more programs recognised. 14 mercenary spyware indicator lists built in so they work offline, 9,014 malicious browser extensions, 2,211 vulnerable or malicious drivers, 200+ remote-access programs, and better reading of iPhone backups from iOS 27.
Fixes since 2.0.7
- A "worth a look" result no longer looks like a clean one, and Windows' own built-in event-log subscription is no longer reported as an attack.
- iPhone backups from iOS 27: installed apps, newer diagnostic reports and large Shortcuts are read again (reported by Natha, #47).
- The doors tool and the report now agree on how many doors are open.
- Saving over an existing file, a damaged picture and an empty option now give a clear message instead of an error.
Thank you to everyone who reported problems and tested on real machines, especially Natha, Verchiel666 and dhruv1220.
Full list in CHANGELOG.md.
Verify before running
zero-breach-toolkit.py SHA-256: e7f8d66ce22c171f3c0f741ce0c0e6f74ffb644b79072f2406725750b9d84639
Each program: gh attestation verify <file> --repo interplains/Zero-Breach-Toolkit.
Checksums and signatures: import the signing key from this release's files first, then verify.
gpg --import archivegenocide-signing-key.asc
gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt
Signed with key C24E C92B 12D6 670A 2516 065F 9B4D 5754 99AF A53C. "This key is not certified with a trusted signature" is normal: it only means you have not signed the key yourself. See docs/VERIFYING.md.
Zero Breach Toolkit 3.0.0
Superseded by v3.0.2: https://github.com/interplains/Zero-Breach-Toolkit/releases/tag/v3.0.2
Zero Breach Toolkit 3.0.0.
More than a spyware check. Version 3 still looks for known spyware, and now also shows the ways in that are left open on your devices and how to close them, checks the links, emails, files and QR codes people send you, and walks you through your accounts, your home network and the trackers and hidden networks around you. Everything runs on your own computer, and nothing leaves it unless you say yes.
Download the file for your computer
| Your computer | Download | The first time you open it |
|---|---|---|
| Windows | zero-breach-toolkit-windows-x64.exe |
Windows may say it "protected your PC". Click More info, then Run anyway. |
| Mac with Apple silicon (M1 or newer) | zero-breach-toolkit-macos-apple-silicon.dmg |
Drag Zero Breach Toolkit to Applications and open it. macOS stops it once: open System Settings → Privacy & Security, click Open Anyway, and open it again. |
| Mac with Intel | zero-breach-toolkit-macos-intel.dmg |
As above. |
| Linux | zero-breach-toolkit-linux-x64.tar.gz |
Extract it and run ./zero-breach-toolkit (add --gui for the window). |
| Any computer with Python | zero-breach-toolkit.py |
The same check in one readable file, for people who want to see exactly what runs. |
The warnings appear because the programs are not yet signed by Microsoft or Apple. Code signing is on its way: the project has been accepted by the SignPath Foundation and the certificate is being issued. Until then, each program is built by GitHub from this release's published source, with a public build record you can check before running it (see Verify below).
What's new
- Doors to close. Every check now lists the ways in that are left open - Remote Desktop, automatic sign-in, no disk encryption, Secure Boot off, browser extensions that can read every site, no ad blocker, an iPhone without a passcode, old Android security updates - each with why it matters and how to close it. "Close the doors found open" can switch some of them off for you, one at a time, after asking, with a way back.
- Check what you were sent. Paste a text, WhatsApp or Signal message or a link; open a saved email; choose a suspicious file or a picture of a QR code. The toolkit says what it really is and whether it matches known spyware or common tricks, without opening, running or following anything. A file can also be looked up online, only if you say yes.
- Was my phone copied? For a phone that was taken from you, for example at a border: signs that it was plugged into a phone-forensics tool such as Cellebrite. Finding nothing is not proof, and the report says so.
- Check your online accounts. A guided list of where to look - devices linked to WhatsApp, Signal, Telegram, Apple, Google and Microsoft, email forwarding, location sharing, a lock on your phone number - starting with the single best thing you can do: sign in with a physical security key. Your answers are kept until you finish.
- Your home and what is around you. Who is on your Wi-Fi and which doors their devices leave open (it asks first); hidden Wi-Fi networks nearby, what each one probably is, and on Windows and Linux a meter that follows one network's signal so you can find the device; Bluetooth trackers such as AirTags that stay near you.
- Look closer at a computer. What starts automatically, explained entry by entry; Windows' own records of hidden commands, downloads that were run and protection switched off; a network recording from a phone, with which company runs each address contacted.
- Live connections, explained. A "Who runs it" column (Google, Microsoft, Cloudflare, Meta, Apple, Amazon and more, from a list built into the program) and a right-click for the program behind each connection, when it started and what started it.
- One report for the household. Put the saved results of every computer, phone and check on one page, worst first, with a list of what has not been checked yet.
- Plain words first. Every result opens with a few lines in plain words: what was found, what it means, what to do. "Not sure where to start?" asks what happened and opens the right check. One button sends the result to someone who can help.
- Every tool in 27 languages. The results of all the smaller tools are now translated too, not only their buttons. Saved results stay in English, the record a helpline works from.
- A friendlier terminal. Choose from the menu with the arrow keys (or type the number), with one progress line and the result in colour.
- More spyware and more programs recognised. 14 mercenary spyware indicator lists built in so they work offline, 9,014 malicious browser extensions, 2,211 vulnerable or malicious drivers, 200+ remote-access programs, and better reading of iPhone backups from iOS 27.
Fixes since 2.0.7
- A "worth a look" result no longer looks like a clean one, and Windows' own built-in event-log subscription is no longer reported as an attack.
- iPhone backups from iOS 27: installed apps, newer diagnostic reports and large Shortcuts are read again (reported by Natha, #47).
- The doors tool and the report now agree on how many doors are open.
- Saving over an existing file, a damaged picture and an empty option now give a clear message instead of an error.
Thank you to everyone who reported problems and tested on real machines, especially Natha, Verchiel666 and dhruv1220.
Full list in CHANGELOG.md.
Verify before running
zero-breach-toolkit.py SHA-256: 5d755bdc8207538ee3007fdaabdf0dc852d82e23de47194a127662d03e859198
Each program: gh attestation verify <file> --repo interplains/Zero-Breach-Toolkit.
Checksums and signatures: import the signing key from this release's files first, then verify.
gpg --import archivegenocide-signing-key.asc
gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt
Signed with key C24E C92B 12D6 670A 2516 065F 9B4D 5754 99AF A53C. "This key is not certified with a trusted signature" is normal: it only means you have not signed the key yourself. See docs/VERIFYING.md.
Zero Breach Toolkit 2.0.7
Superseded by v3.0.2: https://github.com/interplains/Zero-Breach-Toolkit/releases/tag/v3.0.2
Zero Breach Toolkit 2.0.7 is now the main release. Three fixes, all reported by people using the toolkit; the Honor fix was confirmed on the phone it was reported from. If you're on an older version, updating is recommended.
Fixes
- Mac: one damaged app file no longer stops the out-of-date-program check. If a single app in Applications had a loosely written information file, the whole check stopped with "module error: XML declaration not well-formed" and no installed program was checked at all. That one file is now skipped and every other app is still checked. Reported by Natha.
- Android on Honor phones: Honor's App Market is recognised as an app store. Apps installed from it were all reported as hand-installed, so on one phone 56 of 65 such warnings were ordinary store apps, hiding the ones worth a look. Honor split from Huawei in 2020 and its phones do not carry Huawei's store. Reported by Verchiel666; the fix was contributed by dhruv1220.
- Checking a download is now spelled out properly. The verification steps below now say to import the signing key first, show its fingerprint to compare, and explain GPG's "not certified" warning. The key has always been published with every release, but the earlier wording could not work as written. Reported by Natha.
Your antivirus may flag these programs. Antivirus products often wrongly flag new programs that are not code-signed yet, and some flag these. If you downloaded the file from this page, this is a false alarm and you can ignore it: the code is public, and each program has a public build record you can check. Bitdefender has accepted our report and is removing its detection; we are reporting the others, and we have applied for free code signing. If the file came from anywhere else, do not run it and trust the warning.
Downloads and first-launch steps: see the README. Full list: CHANGELOG.
Verify before running
Each program: gh attestation verify <file> --repo interplains/Zero-Breach-Toolkit.
The checksums are also GPG-signed. Import the signing key first - it is in the asset list below, as archivegenocide-signing-key.asc:
gpg --import archivegenocide-signing-key.asc
gpg --verify SHA256SUMS-programs.txt.asc SHA256SUMS-programs.txt
sha256sum --ignore-missing -c SHA256SUMS-programs.txt
For the single Python file, the same with SHA256SUMS.txt.asc and SHA256SUMS.txt.
Compare the key's fingerprint before you trust it: C24E C92B 12D6 670A 2516 065F 9B4D 5754 99AF A53C. GPG will also say the key is not certified with a trusted signature - that is normal, and it does not mean the signature is bad; it only means you have not personally signed the key. Full instructions: docs/VERIFYING.md.
Zero Breach Toolkit 2.0.6
Zero Breach Toolkit 2.0.6 is now the main release. It was published for testing on 5 November, nothing turned up, and the macOS fixes below were confirmed on a real Mac by the person who reported them. If you are on 2.0.4 or earlier, please update: on some Macs the optional pattern check stopped the scan with no message at all, which is fixed here.
New indicators
- SHA-1 sample fingerprints are now used. Where researchers publish a spyware sample only by its SHA-1, the file check, the record of programs Windows has run, and Android app files and file lists now compare SHA-1 as well as SHA-256, from the same single read of each file. Published feeds (STIX and MISP) contribute their SHA-1 sample hashes too.
- More phone spyware, from Lookout: MOONSHINE, Hermit, BouldSpy, KoSpy, DCHSpy, and Massistant — a phone-extraction tool used by police on seized phones.
- Dante (Memento Labs, formerly Hacking Team), from Kaspersky: sample fingerprints, plus, on Windows, a check for the Windows component its loader hijacks and for the module folder layout the report describes. Both are reported as leads to check, not findings.
macOS fixes (reported by s3ba-b)
- The optional pattern check now runs the pattern engine in a separate process first. On some Macs it stopped Python with no message; now the check is skipped with an explanation and the rest of the scan finishes and writes its report.
- When macOS refuses Safari's cookie file or a browser's bookmarks, the report gives the Full Disk Access advice instead of a raw error.
- Two tests no longer fail on Apple's own Python.
Your antivirus may flag these programs. Antivirus products often wrongly flag new programs that are not code-signed yet, and some flag these. If you downloaded the file from this page, this is a false alarm and you can ignore it: the code is public, and each program has a public build record you can check. We have applied for free code signing and are reporting these false alarms to the antivirus companies. If the file came from anywhere else, do not run it and trust the warning.
Downloads and first-launch steps: see the README. Full list: CHANGELOG.
Verify before running
Each program: gh attestation verify <file> --repo interplains/Zero-Breach-Toolkit.
The checksums are also GPG-signed. Import the signing key first - it is in the asset list below, as archivegenocide-signing-key.asc:
gpg --import archivegenocide-signing-key.asc
gpg --verify SHA256SUMS-programs.txt.asc SHA256SUMS-programs.txt
sha256sum --ignore-missing -c SHA256SUMS-programs.txt
Compare the key's fingerprint before you trust it: C24E C92B 12D6 670A 2516 065F 9B4D 5754 99AF A53C. GPG will also say the key is not certified with a trusted signature - that is normal, and it does not mean the signature is bad; it only means you have not personally signed the key. Full instructions: docs/VERIFYING.md.
Zero Breach Toolkit 2.0.5 (pre-release)
Zero Breach Toolkit 2.0.5 (pre-release for testing). If nothing turns up during testing, it becomes the main release.
New
- macOS: the system's record of downloaded files is also searched. A file downloaded from a known spyware address is reported with its date; an address that is only mentioned is a reference. If the record is missing or can't be read, it's listed as not checked. Contributed by s3ba-b.
Safer updates
- The list of actively exploited software now has the same protection as the indicator lists: a download with fewer than half the entries this computer has seen before is refused, and the previous copy is kept.
More thorough
- Only this project's own published blocklist files are treated as filter lists. Anything else cached from our sites is searched like any other page.
Other
- The programs' checksums are signed with the release key; see VERIFYING.md.
- Tests no longer run twice for the same branch. Contributed by zaccromero.
Your antivirus may flag these programs. Antivirus products often wrongly flag new programs that are not code-signed yet, and some flag these. If you downloaded the file from this page, this is a false alarm and you can ignore it: the code is public, and each program has a public build record you can check. We have applied for free code signing and are reporting these false alarms to the antivirus companies. If the file came from anywhere else, do not run it and trust the warning.
Downloads and first-launch steps: see the README. Full list: CHANGELOG.
Verify before running
zero-breach-toolkit.py SHA-256: d3d50bda337d33536512d42f139fcb72f6c9bac212eae6b5ef8824cb06f62c96
Each program: gh attestation verify <file> --repo interplains/Zero-Breach-Toolkit. Their checksums are also GPG-signed: gpg --verify SHA256SUMS-programs.txt.asc SHA256SUMS-programs.txt, then sha256sum --ignore-missing -c SHA256SUMS-programs.txt. Signed with key C24E C92B 12D6 670A 2516 065F 9B4D 5754 99AF A53C.
Zero Breach Toolkit 2.0.4
Zero Breach Toolkit 2.0.4. Fixes from real Mac and Windows runs. Thanks to the people testing it.
If you are on 2.0.0 to 2.0.2, please update, and if the window showed a phone as green, check it again: those versions could say more than the check had done (2.0.3 fixed that).
Mac
- No more false "macOS is out of date" warning. A date in a vulnerability record was being read as a version number, so every current Mac got it. Thanks to s3ba-b for finding it.
- Safari folders that macOS refuses now give the plain privacy message, and the Full Disk Access advice is left out when access is already on.
Windows
- Double-clicking no longer leaves a terminal in the taskbar, which ended the check if you closed it.
- The Quick check estimate is now 5 to 15 minutes, and connections that are closing are labelled "System" instead of "System Idle".
- Chinese, Japanese and Korean use the matching Windows font.
Everyone
- The report's date comparison names the AdFection campaign, rather than implying the tool looks for only one campaign.
- A check that does not apply says why in the report's detail.
- A stopped check no longer says "nothing matched" in its next steps.
- The saved report's location shows on the Result tab, and the save dialog lists file types.
- Help scrolls and fills its tab, and Japanese and Chinese wrap correctly there. Right-to-left lines leave more room in small windows.
Your antivirus may flag these programs. Antivirus products often wrongly flag new programs that are not code-signed yet, and some flag these. If you downloaded the file from this page, this is a false alarm and you can ignore it: the code is public, and each program has a public build record you can check. We have applied for free code signing and are reporting these false alarms to the antivirus companies. If the file came from anywhere else, do not run it and trust the warning.
Downloads and first-launch steps: see the README. Full list: CHANGELOG.
Verify before running
zero-breach-toolkit.py SHA-256: 98279a7212220260f78e72020e52420565cc6c0c00f25bb02d478902288b80fc
Each program: gh attestation verify <file> --repo interplains/Zero-Breach-Toolkit. Their checksums are also GPG-signed: gpg --verify SHA256SUMS-programs.txt.asc SHA256SUMS-programs.txt, then sha256sum -c SHA256SUMS-programs.txt. Signed with key C24E C92B 12D6 670A 2516 065F 9B4D 5754 99AF A53C.
Zero Breach Toolkit 2.0.3
Superseded by 2.0.4.
Zero Breach Toolkit 2.0.3. Please update.
If you checked a phone with 2.0.0, 2.0.1 or 2.0.2 and the window showed green, please check it again. A code review found that some results said more than the check had done.
Results that said too much
- A phone nothing could be read from could show green. This happened with an empty folder when a phone type was chosen, a damaged sysdiagnose, or an Android collection with an empty app list. It now says "This phone could not be checked".
- Green now means nothing matched and every check ran. If some checks could not run, the window says "Nothing found in what could be checked" in a neutral colour and lists them. Expect to see this more often than green: many computers and phones have something that cannot be checked, and a missing check is not a clean result.
- Android crash records in current and older layouts are now read. A record that cannot be read is listed as not checked. Removed apps are now recognised in real battery history.
- A file in a layout the tool does not recognise is listed as not checked instead of being counted as read.
- The report says which file types the Standard check did not fingerprint, and a match in a phone log gives its line number and says that a mention is not proof of contact.
Other fixes
- "Update indicator lists" no longer shows "name 'feeds' is not defined". The lists were updating; the error message was wrong. Thanks to the Mac and Linux testers who reported it.
- The phone guides in the programs describe the window's own buttons, not terminal commands.
- Saving a report opens in Downloads, and explains what to do if security software blocks the save.
- Help uses the real button names in your language, and right-to-left text displays better.
- A network path pasted into the phone folder box is refused before anything contacts that server, and a planted named pipe can no longer hang the check on Linux or Mac.
- A damaged archive and very long crafted text are handled more safely.
Your antivirus may flag these programs. Antivirus products often wrongly flag new programs that are not code-signed yet, and some flag these. If you downloaded the file from this page, this is a false alarm and you can ignore it: the code is public, and each program has a public build record you can check. We have applied for free code signing and will report these false alarms to the antivirus companies. If the file came from anywhere else, do not run it and trust the warning.
Downloads and first-launch steps: see the README. Full list: CHANGELOG.
Verify before running
zero-breach-toolkit.py SHA-256: 4dfeeb805fcd74fd476369566659b0aeb5ebc91438f537f4ad2865264e1867d4
Each program: gh attestation verify <file> --repo interplains/Zero-Breach-Toolkit. Signed with key C24E C92B 12D6 670A 2516 065F 9B4D 5754 99AF A53C.
Zero Breach Toolkit 2.0.2
Superseded by 2.0.3. Please update: if this version showed a phone as green, check it again with 2.0.3.
Your antivirus may flag these programs. Antivirus products often wrongly flag new programs that are not code-signed yet, and some flag these. If you downloaded the file from the official release page, this is a false alarm and you can ignore it: the code is public, and each program has a public build record you can check. We have applied for free code signing and will report these false alarms to the antivirus companies. If the file came from anywhere else, do not run it and trust the warning.
Zero Breach Toolkit 2.0.2.
Fixes
- No more crash when a window can't be opened. On a Mac, trying to open the window could end the whole program ("Python quit unexpectedly"): in a remote session, and on a normal desktop with Apple's own built-in Python on some macOS versions. The check now says the window could not be opened and carries on in the terminal. On Apple's Python it also suggests installing Python from python.org.
- Clearer download steps. The README now has numbered steps for Windows, Mac and Linux, says which check to choose, and explains what a green result does and does not mean.
- German: one sentence no longer leaves an English word in it.
- For contributors: the test suite now copes with Apple's Python, and a single test file can be run on its own. Thanks to the Mac tester who reported these.
Nothing changed in what the check looks for. If you use 2.0.0, please update: it could not open encrypted iPhone backups (fixed in 2.0.1).
Downloads and first-launch steps: see the README.
Verify before running
zero-breach-toolkit.py SHA-256: bcf8459d0a6d7ecb1612e25c23abf6c676d02e086cd8af6bd7d8c7524df20aec
Each program: gh attestation verify <file> --repo interplains/Zero-Breach-Toolkit. Signed with key C24E C92B 12D6 670A 2516 065F 9B4D 5754 99AF A53C.
Zero Breach Toolkit 2.0.1
Superseded by v2.0.2: https://github.com/interplains/Zero-Breach-Toolkit/releases/tag/v2.0.2
Zero Breach Toolkit 2.0.1.
Fix: encrypted iPhone backups. The 2.0.0 programs could not open an encrypted iPhone backup and could then show "No known spyware traces found". The programs now include the library needed to open them, and a phone backup that cannot be read now shows as "This phone could not be checked", never as clean. If you checked an encrypted iPhone backup with a 2.0.0 program, please check it again with 2.0.1.
Downloads and first-launch steps: see the 2.0.0 release notes.
Verify before running
zero-breach-toolkit.py SHA-256: 0044b2773561711d74bbb432034d34b429a5cbe0d28d30d4747389487cbaabac
Each program: gh attestation verify <file> --repo interplains/Zero-Breach-Toolkit. Signed with key C24E C92B 12D6 670A 2516 065F 9B4D 5754 99AF A53C.