Security
Found a vulnerability? Tell us.
An antivirus has to be trustworthy, so we take security reports seriously and we are grateful to the people who send them. This page explains how to report a problem and what you can expect from us.
Last updated October 21, 2026.
In scope
- The website at anakrio.com, including registration, renewal, download and the public API under /api/.
- Anakrio for Windows: the installer, the update and license mechanisms, real-time protection, quarantine and the handling of rule files.
- Integrity of the signature feed and of the installer checksums we publish.
Out of scope
- A specific piece of malware that Anakrio does not detect, or a harmless file it flags. That is a detection problem, not a vulnerability: please use the detection report form.
- Denial-of-service, volumetric or load testing, spam and brute-force traffic.
- Social engineering or phishing of our team or our users, and physical attacks.
- Reports that need an already compromised computer or administrator rights on the victim PC.
- Automated scanner output without a working proof of concept, and missing headers or best-practice settings without a demonstrated impact.
- Third-party services such as our hosting provider, our email provider and the abuse.ch feeds.
What to include
- A clear description of the issue and why it matters.
- Step-by-step instructions to reproduce it, ideally with a minimal proof of concept.
- The affected URL, endpoint or Anakrio version.
- Your contact details, so we can ask questions and credit you if you wish.
Ground rules
- Only test with your own license and your own data. Do not access, change or delete other people's data.
- Stop as soon as you reach personal data and tell us what you saw. Do not copy or keep it.
- No denial-of-service, spam, social engineering or destructive testing.
- Give us reasonable time to fix the problem before you publish details.
What you can expect from us
We reply quickly
We aim to acknowledge every report within three business days and to keep you updated until it is resolved.
We fix what matters
Confirmed vulnerabilities are fixed as soon as we can, serious ones first, and fixed versions are announced in the changelog.
We give credit
If you want, we name you on this page once the issue is fixed. You can also stay anonymous.
We act in good faith
If you follow this policy, we treat your research as authorized and will not take legal action against you for it.
We do not run a paid bug bounty at this time. Recognition on this page is the reward we can offer today.
How we keep Anakrio secure
- All traffic uses HTTPS, and signature updates are fetched over verified HTTPS.
- A strict content security policy, no inline scripts and CSRF protection on every form.
- Rate limits and bot filters on registration, renewal and reporting.
- License keys are stored only as hashes, and one-time renewal links expire after 30 minutes.
- Passwords in the admin area are hashed and two-factor login is supported.
- Published SHA-256 checksums for every installer.
Thanks to
No public reports have been credited yet. Be the first.
See also: Privacy · Terms · System status