Hash signatures
MD5, SHA-1 and SHA-256 of known-bad files, computed in a single streaming pass. Exact matches, so zero false positives — but only for that exact build.
The complete list, grouped the way the product is built.
Four independent layers. Any one of them can convict a file.
MD5, SHA-1 and SHA-256 of known-bad files, computed in a single streaming pass. Exact matches, so zero false positives — but only for that exact build.
A hex or ASCII fragment that must appear in the file, optionally anchored to a magic value. Survives trivial repacking and covers whole families.
Native yara-python when installed. Without it, a built-in interpreter
handles the bundled rule subset — and skips anything it cannot parse, so a missing
dependency can never invent a false positive.
Scored rules summed against a threshold you control — but an alarm always needs one construct that is specific to malware.
invoice.pdf.exeEntropy, packing, embedded base64 and process-injection API imports only ever corroborate one of the above. On their own they describe a game asset bundle or a launcher log just as well.
ZIP members are scanned in memory, never unpacked to disk. Flags zip bombs by compression ratio and members that escape the extraction directory.
13 YARA rules covering reverse shells, ransomware, infostealers, keyloggers, process injection, miners, cron persistence and macro droppers — plus a baseline signature set and two harmless self-test files.
What runs continuously, and what you trigger.
Threats are moved out of reach and stored inert under a per-install key. They cannot execute, and they will not trip other on-access scanners while parked.
Reversible on purpose. Every entry restores byte-for-byte, because false positives happen and you should not lose a file to one.
| Action | What happens |
|---|---|
| Quarantine | File is moved to the vault and obfuscated |
| Restore | Written back to its original path and permissions |
| Delete | Overwritten, then removed permanently |
| Empty | Clears the whole vault |
| Retention | Entries expire automatically by age and count |
Unpatched software is the most common way a machine gets compromised.
Finds outdated software across every package manager on the machine.
Point it at a JSON manifest and it keeps itself current.
Two front ends over one engine, so they can never disagree.
--json on every commandGUARDIANTUS_HOMEFileScanner directlyThe dashboard can quarantine files and install packages, so it is treated as a real attack surface.
| Control | Attack it stops |
|---|---|
| Loopback bind | Remote access to the API |
| Per-run session token | Other local processes driving it |
| Host header validation | DNS rebinding — a visited page controlling your local API |
| Origin validation | Cross-origin requests |
| Strict CSP, no inline script or style | Injected-content execution |
| Resolve-and-recheck static paths | ../ directory traversal |
| Fixed argv, validated package ids | Command injection via package names |
The Threat Lab runs the same detection logic in your browser. Nothing is uploaded.