ZSEC Antivirus Community
A Windows protection dashboard for Windows Security and Defender evidence plus fixed Defender update/scan actions, bounded second-opinion checks, automatic post-change folder monitoring and encrypted quarantine.
ZSEC Antivirus 0.3.14 · ZSEC Browser 0.3.15 · Browser Shields 0.5.2
Security tools you can inspect, verify and understand.
ZSEC combines a Defender-backed Windows protection control plane, local post-change file monitoring, authenticated encrypted quarantine, an unsigned WebView2 browser shell and an auditable Manifest V3 request layer. Exact release bytes are identified by immutable revision, byte size, SHA-256 and applicable runtime evidence—not by version text alone.
Protection boundary: Microsoft Defender remains the supported Windows real-time enforcement provider when live evidence confirms it active. ZSEC is unsigned, user-mode and post-change; it is not a registered primary antivirus, protected service, kernel pre-access provider, maintained Chromium fork or Pegasus-immunity product.
Evidence before claims
Three focused surfaces
Choose the layer that matches the job.
Each product has a separate decision point and a separate evidence boundary. Combining them adds useful layers; it does not create universal exploit, malware or spyware protection.
ZSEC Browser Community 0.3.15
An unsigned Windows WebView2 shell with managed tabs, bookmarks, bounded local history suggestions, seven search providers, a separate profile, native document/subresource controls and a user-operated local encrypted password vault. The vault does not autofill pages or sync to ZSEC.
Browser Shields 0.5.2
An inspectable Manifest V3 layer with 49,464 pinned EasyList network rules, 39 focused privacy rules, two tracking-link cleaners and an optional two-rule High-Risk Browsing profile.
Release contract
Verify the artifact, not just the name.
Release v0.3.14 points to immutable source revision 57557ae4dd03765a59b05a3a0e0006edc13b7bd4. Its release pages name exact bytes only after clean-build, package-contract and applicable installed-runtime gates pass.
1. Match the revision
Confirm the release points to one immutable source commit and the intended annotated tag.
2. Match bytes and hash
Compare the published byte size and SHA-256 locally. Any mismatch is a stop condition.
3. Read the evidence
Separate workflow tests, provenance attestations and installed-runtime acceptance instead of treating them as interchangeable.
4. Keep platform controls
Keep Defender or another supported primary provider, WebView2 updates and native operating-system protections active.
Canonical release evidence
Open the v0.3.14 release · ZSEC Antivirus downloads · ZSEC Browser downloads · Machine-readable product boundaries
Honest security boundary
Useful protection without immunity theatre.
ZSEC Browser's YouTube handling is best effort and can be evaded by site changes. High-Risk Browsing reduces two documented request classes but does not detect Pegasus, inspect memory or stop an unknown zero-click chain. ZSEC Antivirus observes selected filesystem changes after the event; it does not supply ZSEC-native kernel pre-access or memory enforcement.
- Defender is named as the Windows real-time provider when verified.
- WebView2 is Microsoft-maintained, not a ZSEC Chromium fork.
- ZBA records typed lifecycle and provenance; established cryptography provides security.
- Unsigned status, runtime scope and unverified platforms remain visible.
Windows enforcementMicrosoft Defender when confirmed active
ZSEC desktopEvidence, safe actions and post-change companion
Browser layerBounded local request and interface controls
No layer establishes a clean-system, spyware-immunity or universal-ad-blocking verdict.
Start with evidence
Read the boundaries. Verify the bytes. Keep control.
The canonical TalkToAI pages explain the user experience; GitHub provides source, release metadata, checksums and provenance.