Changelog
What's New
Release history for InfinityGuard. Every version, every fix, every improvement — documented here.
-
AI Defense now requires scanner corroboration before quarantining.
Previously, the AI Behavioral Engine could quarantine files at high confidence without ClamAV, YARA, or HashDB confirmation. All AI detections now require at least one scanner to confirm before any file is quarantined — eliminating false positives on unsigned or packed executables.
Root cause: the real-time monitor called the AI engine directly, bypassing the scanner's skip-list entirely.
-
Unconfirmed AI detections logged as LOW severity instead of being silently dropped. These entries appear in the Threat Log with a "possible false positive" note and are automatically sent to ThreatVerifier, which runs ClamAV + Windows Defender and updates the entry with a verdict.
-
In-progress downloads no longer flagged by real-time protection.
Files with
.crdownload, .part, or .download extensions — and .tmp files inside the Downloads folder — are now skipped by the behavioral engine until the download completes. Chrome and Edge write to these temp paths during download.
-
New InfinityGuard shield icon replaces the generic blue square. All three sizes (16×16, 48×48, 128×128) now show a proper gradient shield on a dark background — consistent with the app's visual identity.
-
Fixed warning overlay not appearing on fast page loads.
The content script initializes at
document_start — before the DNS check completes. The background's fallback now calls window._igShowWarning() directly instead of setting a variable the content script had already walked past.
-
Download threats now appear in the Activity Log with the threat name and detection engine, matching how real-time file threats are reported.
-
New LOW severity tier in the Threat Log.
Unconfirmed AI detections appear as muted entries clearly labeled "Possible False Positive" — visually distinct from HIGH and CRITICAL. These are automatically updated once ThreatVerifier finishes its check.
-
Patch-script backup files excluded from the installer package.
.bak and .bak_* files generated by prior patch scripts were being bundled inadvertently. These are now excluded from both the Inno Setup package and the build sync step.