vulnix0x4/a-better-antivirus
Security & PrivacyWindows tripwire tool that plants fake credentials and app data to catch infostealers and freeze them on access.
What it does
A Better Antivirus (ABA) is a Windows detection tool aimed at infostealers such as Lumma, RedLine and Vidar. Instead of scanning files or matching signatures, it places decoy credentials, wallet seeds, browser profiles and app data in locations that stealers read. A decoy read triggers a freeze on the reading process, usually within about 0.1 s when instant freeze is enabled. The owner can then trust, kill or resume the process. It runs on Windows 10 and 11, is written in Go and is MIT licensed.
The tool is intended as a tripwire for threats that already got past traditional antivirus, not as a replacement. The README explicitly says to keep Windows Defender enabled. It targets users who want to detect stealer activity on their own machine and can respond to desktop or phone alerts.
Quick start
In an elevated PowerShell session on Windows, run the installer:
irm https://raw.githubusercontent.com/vulnix0x4/a-better-antivirus/main/install.ps1 | iex
The script downloads the latest release, checks it against SHA256SUMS.txt, and starts setup. The recommended path asks only about phone alerts and automatic updates; the custom path lets you choose baits and responses. Setup offers a safe test that runs a harmless fake stealer against a bait so you can see the freeze behavior.
After setup, aba is available in the same window. Running aba shows a live dashboard, aba test runs the safe simulation, aba alerts lists what touched the baits, and aba doctor checks that everything is armed.
Manual installation is also possible: download the Windows amd64 or arm64 executable from releases, verify the SHA-256 against SHA256SUMS.txt, and run it with install. Releases are not code-signed yet, so SmartScreen may warn about the file.
Detection model
Two paths detect a bait access. Instant freeze holds an opportunistic lock on every bait, so Windows pauses a program the moment it opens one and tells ABA immediately. A backup path uses Windows NTFS file auditing and Security event 4663, which also catches programs that avoid the pause. Before acting, ABA applies an automatic severity verdict from path, name, signature and behavior: unsigned binaries in user-writable folders, script hosts, injected code and sweeps across several apps' data are treated as critical. Signed legitimate apps are unfrozen and noted.
Responses follow presets. Balanced freezes a critical reader and blocks its network access; Strict also isolates the PC using Windows Filtering Platform. aba trust, aba kill, aba resume and aba release undo or extend the response. Trust is narrow: it is pinned to the specific bait, signer, file hash or exact command line, so injected code in a trusted app that reads other baits is still caught.
Constraints
- ABA is a tripwire, not a shield. A stealer that only reads real browser data and never touches a bait is not detected.
- Anti-evasion depends on the stealer not knowing which files are baits. The names differ per install and ABA's own records are restricted, but a stealer can be written specifically to recognize ABA or to read only each browser's listed profiles.
- Instant freeze typically stops a stealer about 0.1 s after the open; a stealer that uploads each item immediately may get some data out first. Without instant freeze, detection relies on the event log, which can take a few milliseconds to about a second.
- Malware running as administrator can stop the service, clear audit policy or remove firewall filters. ABA alerts if auditing is switched off but cannot defend against an attacker who already has admin rights.
- Injection is judged by results, not observed directly; no kernel driver is used. Windows desktop processes are never frozen, only cut off from the network.
- Desktop popups require a signed-in session. Some legitimate software, such as backup and sync tools, reads files in ways that look like a sweep; these must be allowed explicitly.
- Several commands require administrator rights because bait metadata is access-restricted. Uninstall removes the program, service, audit policy, baits and firewall filters, and keeps alert history unless
--purgeis passed.
Data and privacy
Network traffic is limited to configured phone alerts, optional canary-token creation with an email address sent to canarytokens.org, and a daily GitHub API request when automatic updates are enabled. No telemetry is described in the README. Automatic updates require an ed25519-signed SHA256SUMS.txt and a matching hash, with rollback if the new version fails to start.
HotRepo's take
The repository entered the Go new-project list on 2026-11-21, with 7 stars gained over a three-hour observation window and 2 forks in the same period. No overall GitHub daily rank is recorded. The project mixes a Windows-specific detection design with an installer and a documented test path; the honest limitations section names cases it does not catch, which helps readers judge whether a tripwire model fits their threat. The release binaries are unsigned, so verification before running is part of the documented workflow rather than an optional courtesy.
Written by AI from the project's public information and HotRepo's records, updated . The project's own docs are the source of truth.