What the sources actually say
The original project is bol-van/zapret on GitHub: a standalone, multi-platform anti-DPI tool whose official English documentation describes its desync mechanisms, hostlists and filters. For Windows users, the widely used build is Flowseal/zapret-discord-youtube, and its README makes a provenance statement that matters for safety: all executable and system files in its bin folder are taken from bol-van's zapret-win-bundle and zapret releases, and you can verify this yourself using hashes and checksums.
The same Flowseal README carries two explicit fraud warnings. First, the author states they run no other pages, Telegram groups or YouTube channels, and that anything distributed in their name outside the GitHub page is fake. Second, it advises checking what you run when using builds found on the internet, and warns against relying on Yandex Search because it often surfaces malware in the top results while hiding the real repository.
The klaymm practical guide repeats the warning in stronger terms: numerous third-party zapret builds distributed via Telegram and YouTube contain malicious code, and downloads should come only from the official Flowseal repository releases. The guide also states its own provenance openly — the original tool is bol-van/zapret, the Windows build it relies on is Flowseal/zapret-discord-youtube — which is exactly the kind of attribution a trustworthy resource provides.
How to verify a build, step by step
- Check the URL before anything else: the official sources are github.com/bol-van/zapret and github.com/Flowseal/zapret-discord-youtube. Anything else is a mirror, a fork or an impostor until proven otherwise.
- Download from the Releases section of those repositories, not from links in chat messages, video descriptions or search ads — the klaymm guide attributes malicious builds to exactly those channels.
- Use the provenance statement: the Flowseal README says its binaries come from the bol-van zapret-win-bundle and zapret releases, so you can compare hashes and checksums against those upstream files.
- Cross-check community claims against the live issue tracker — the Flowseal issues index shows active, dated reports, and a repository with no visible issue activity around a zapret build is a red flag rather than a sign of polish.
- Be suspicious of any build that asks you to disable security software without explanation, or that ships executables whose upstream origin you cannot identify.
- When in doubt, prefer the smallest verifiable path: the bol-van releases or zapret-win-bundle directly, which the Flowseal README itself cites as its binary source and as an alternative build.
This is also why this site links you to the upstream releases instead of hosting repackaged binaries. A repack would insert an unverifiable step between you and the author, break the checksum comparison the Flowseal README invites you to perform, and go stale the moment a new upstream release ships. Linking upstream keeps every byte you download attributable to a project you can inspect.
What is source-backed vs community-reported
- Source-backed (official repository): bol-van/zapret is the original project, and its documentation defines what the tool actually does.
- Source-backed (build README): the bin-folder provenance statement with hash verification, the fake-channel warning, and the search-engine malware warning are published by the Flowseal maintainer.
- Source-backed (practical guide): the klaymm guide states that third-party Telegram/YouTube builds contain malicious code and names its own upstream sources.
- Community-reported: individual fake-build sightings discussed in the tracker are user reports; the index itself, not any single story, is what we cite.
When the reported workaround may not apply
Verification steps differ by platform: the checksum workflow described for the Windows build assumes the documented upstream binary source, and other platforms install from the main repository's own scripts and releases instead. Legitimate forks and bundles exist — the Flowseal README itself points to zapret-win-bundle — so an unofficial URL is a prompt to verify, not automatic proof of malice. And no download hygiene changes the technical reality that Zapret does not guarantee access for every ISP or region; safety guidance and effectiveness are separate questions.