Skip to content

Hypatia Scans Android Malware With

Hypatia Scans Android Malware With

Hypatia vs Google Play Protect: why this offline Android signature scanner isn't a drop-in replacement, plus update gaps, false positives, F-Droid permissions.

App summary

App
Hypatia
Developer
Divested Computing Group
License
GPL-3.0-only
Version
unknown
Size
unknown
Price
Free

Hypatia is an Android malware scanner from Divested Computing Group, released under GPL-3.0-only and distributed through F-Droid. It does two things: it monitors files in real time, and it matches files and installed apps against malware signatures. That is the whole product, and the fact that the description is so short is the most useful thing to understand about it. This is not a security suite, not a cloud service, and not a replacement for the protections Google builds into Android. It is a free, auditable signature scanner that runs offline and asks nothing of you in the way of an account.

The rest of this review is organized around the questions people actually arrive with: how it compares to Play Protect, what happens when a signature update misses something or flags the wrong file, what it scans and what permissions it needs, and whether real-time monitoring costs you battery. Where the project has not published an answer, this article says so instead of guessing.

Hypatia vs Google Play Protect: Why an Offline Signature Scanner Is Not a Drop-In Replacement

Start with the mechanism. Hypatia performs signature-based detection of malicious files and installed apps. A signature is a known pattern; the scanner compares what is on your device against a database of those patterns. This is a well-understood approach, and it is genuinely useful for catching malware that someone has already identified and fingerprinted. It is also, by construction, a method that cannot recognize something it has never seen described. The fact data is explicit about this: Hypatia is not a full-featured antivirus suite with cloud or behavioral analysis. There is no component watching how an app behaves after it launches, and no remote service being consulted when a file looks unfamiliar.

That distinction matters most in the comparison people instinctively make. Google Play Protect is part of the Android platform and operates with visibility that an installed app does not have. Hypatia is an app you add. Framing it as a drop-in replacement inverts the relationship: one is a platform service, the other is a scanner with a specific, narrow detection method. The fact data does not describe how Play Protect behaves, what it detects, or how it would respond to the same file, so any side-by-side detection comparison would be invented. What can be stated is Hypatia’s own boundary — signature matching only, no cloud analysis, no behavioral layer — and that boundary is what makes the “replacement” claim wrong regardless of what Play Protect does or does not catch.

The zero-day problem follows directly. Signature-based detection has limited ability to catch unknown or zero-day malware, and detection quality depends on signature database freshness. A brand-new malicious APK that has not yet been fingerprinted will very likely pass a Hypatia scan. That is not a bug in the implementation; it is the nature of the method. Users who install Hypatia expecting it to intercept a freshly built, previously unseen trojan are going to be disappointed, and the disappointment will be their own fault for misreading what the app claims to do.

There is a real argument for the offline design, and it deserves to be stated without turning into a slogan. Hypatia is designed for offline signature-based scanning and does not require an account. Nothing in the fact data describes uploading suspicious files anywhere. For a user who does not want a security product tied to a cloud account, that is a meaningful property. It is not, however, a claim of superior protection. Offline scanning trades away the responsiveness that a cloud-backed system can offer in exchange for not depending on one. Whether that trade is worth it depends entirely on the threats you face and how much you trust the signature feed — a subject the next section takes up.

Hypatia Signature Updates and False Positives: What Happens When an APK Is Missed or Flagged

Detection quality depends on signature database freshness. That single sentence from the fact data carries most of the operational weight here. A signature scanner is only as current as its database, and the fact data does not specify where those signatures come from or how often they are refreshed. There is no published cadence to quote, no upstream feed named, no update interval to plan around. Anyone telling you Hypatia updates hourly, daily, or weekly is working from something other than the project’s own documentation. The honest position is that the update mechanism exists because the app is distributed and maintained, but its rhythm is not something this review can state.

What follows from that is the clean-scan trap. Because signature-based detection has limited ability to catch unknown or zero-day malware, a scan that reports nothing is not proof that an APK is safe. It is proof that the file did not match anything in the database at the moment of scanning. Those are very different statements, and conflating them is how people get hurt. If you sideload an APK from a source you do not trust and Hypatia stays quiet, you have learned that the file is not a known sample. You have not learned that it is benign. Treat a clean result as one data point among several, not as a clearance certificate.

The reverse case is just as important and considerably less discussed. False positives happen with signature matching, and the fact data does not document how the project handles them. There is no stated process for disputing a flag, no described channel for submitting a sample that was wrongly identified, and no published guidance on what a user should do when a legitimate app is quarantined or blocked. Missed detections are in the same category: the fact data does not describe a reporting path for malware that Hypatia failed to catch. This is a genuine gap, and pretending otherwise would be dishonest.

Where should you look, then? The project’s official surfaces. Hypatia’s source is hosted on GitHub at Divested-Mobile/Hypatia, and it is distributed via F-Droid. Those two places are where update guidance and any reporting conventions would live, and they are the only places a reader should trust for current information. If you hit a false positive or believe a scan missed something, check the repository and the F-Droid listing rather than relying on forum posts or secondary write-ups. The project may well have conventions for both; this review simply cannot assert what they are, and you should confirm against the source rather than assume.

What Hypatia Scans by Default—and Which Android Permissions You Must Verify on F-Droid

The stated scope is real-time file monitoring plus signature-based detection of malicious files and installed apps. Two categories, then: files, and apps that are already installed. Real-time monitoring implies a persistent watch rather than a one-shot scan you trigger manually, though the fact data does not describe the exact mechanics of how that monitoring is implemented or what it covers at the filesystem level. What it does establish is that the app is doing continuous work, not sitting idle until you press a button.

The question almost everyone asks next is whether sideloaded APKs and files sitting in internal storage are covered by default. The fact data does not specify this. It does not say that sideloaded APKs are scanned, and it does not say they are excluded. It does not enumerate which storage locations fall inside the monitoring scope. Given that sideloaded APKs are precisely where a signature scanner earns its keep on Android, this is an uncomfortable blank, and the only responsible advice is to verify coverage yourself rather than assume it. Install the app, check its settings and any documentation linked from the official listing, and confirm what is actually being watched before you rely on it.

Permissions are the same story. The fact data does not list Hypatia’s permission requirements. File monitoring on modern Android is permission-sensitive — scoped storage changed what an app can see without explicit grants — and the specific set Hypatia requests is not recorded here. The privacy note in the fact data is direct about the remedy: verify current permissions on F-Droid before installing. That is not a formality. The F-Droid listing shows the permissions an APK declares, and reading them tells you more about what the app can actually reach than any general description will.

One misconception needs to be killed here, because it recurs constantly. Root is not stated as a requirement anywhere in the fact data. Hypatia is not described as a root-only tool, and there is no indication that it depends on elevated privileges to perform its stated function. If you have read that Hypatia only works on rooted devices, that claim is not supported by the project’s own materials as captured here. Whether an unrooted install achieves full coverage of every file on the device is a separate and unanswered question — but “requires root” and “may not see everything without broad permissions” are not the same claim, and only the second one is plausibly in play.

Hypatia Real-Time Scanning on a Full Phone: Battery and Scan-Speed Claims vs What Is Actually Known

The only performance statement available is that Hypatia takes a lightweight real-time scanning approach. That is a description of design intent, not a measurement. There is no published battery impact figure, no scan throughput number, no time-to-complete for a full device, and no APK size to help you estimate what you are adding. The fact data lists the APK download size as unknown, the minimum supported Android version as unknown, and the latest version number as unknown. Anyone quoting milliamp-hours or minutes per scan is making it up.

What can be reasoned about is where the load comes from. Real-time file monitoring means the app is doing work as files change, and signature matching means comparing content against a database. Performance will depend on factors such as signature database freshness and on device storage or app count — a phone with tens of thousands of files and hundreds of installed apps presents a different workload than a nearly empty one. The fact data does not supply thresholds for any of this, so there is no basis for saying a particular device will or will not notice the overhead.

The practical consequence is that you have to test it yourself. Install Hypatia from its official distribution, use the phone normally for a while, and watch your own battery stats rather than trusting a generic claim about lightweight scanning. This is not a dodge; it is the only honest method when the developer has not published figures and this review has not run a benchmark. Device variance on Android is enormous, and a number measured on someone else’s hardware would tell you very little about yours.

Compatibility deserves the same caution. The fact data does not state a minimum Android version, which means it cannot confirm behavior on Android 14 or Android 15, or on anything else specific. The F-Droid listing is where the current version, the required Android level, and the download size would be visible, and that listing is the thing to check before you install — not a review, and not a forum thread from an unknown date. People running very old or otherwise unsupported Android builds are in the wrong audience for this app until the listing says otherwise.

What the GPL-3.0 License and the GitHub Repository Actually Buy You

Hypatia is released under GPL-3.0-only, and its source is hosted on GitHub at Divested-Mobile/Hypatia. Those two facts are the substance behind the word “open source” as applied here. The license is a specific one with specific obligations: anyone distributing a modified version must do so under the same terms, and the source must remain available. That forecloses the proprietary-fork path. It also means the code you install can, in principle, be read by anyone who wants to check what it does.

Auditability is the practical benefit, and it is worth being precise about what it does and does not mean. Open source and auditable means the code can be examined. It does not mean it has been examined by you, or that examination has found nothing wrong, or that the project has a security review process. Those would be separate claims and the fact data supports none of them. What you get is the absence of a closed box — the ability to verify rather than trust — and for a certain kind of user that is the entire point.

The license also tells you something about the project’s posture. GPL-3.0-only is a copyleft license chosen deliberately; it is not the default for a quick utility. Combined with free distribution and no account requirement, it describes a project built to be inspectable and to stay that way. None of this makes the detection engine better. A permissively licensed scanner and a copyleft scanner with the same signature database catch exactly the same files. The license affects your ability to trust the implementation, not its hit rate.

What the license does not buy you is support, a service-level commitment, or any guarantee about signature coverage. There is no commercial relationship here and no vendor to escalate to. If the signature feed goes quiet or a false positive goes unresolved, your recourse is the repository and the F-Droid listing. That is the trade for a free, auditable tool, and it is a trade a technical user can make comfortably and a non-technical one probably cannot.

The Missing Specs: Version Number, APK Size, and Minimum Android Version

Three basic facts about Hypatia are not established: the exact latest version number and release date, the APK download size, and the minimum supported Android version. These are not obscure details. They are the things you would check before installing any app, and their absence from the available record is a real limitation on what this review can tell you. It also means any article that quotes a version number or a file size for Hypatia is either working from a listing that has since changed or is guessing.

Why does it matter? Version number and release date tell you whether the project is actively maintained. A scanner whose signature database depends on freshness is a scanner whose maintenance cadence is a security property. Without a version history you cannot assess that from the outside. APK size tells you what you are adding to your storage and gives a rough sense of complexity. Minimum Android version tells you whether the thing will install at all. Each of these is a normal pre-install check, and each is unanswered here.

The remedy is unglamorous and effective: look at the F-Droid listing before you install. That listing carries the current version, the size, and the Android compatibility information, and it is updated by the distribution process rather than by a review written at a fixed point in time. The same applies to the GitHub repository, which is where release information originates. If the numbers matter to your decision — and for compatibility they should — get them from those two places on the day you install.

Users on unsupported or very old Android versions should read this as a warning rather than a formality. With no stated minimum, there is no basis for promising the app will run on an old device, and no basis for promising it will behave correctly on the newest release either. That uncertainty is not a mark against the app; it is a mark against installing blind.

Five Hypatia Misconceptions That Keep Circulating

Hypatia is not a full security suite. There is no firewall, no VPN, no call blocker, no anti-theft, no web protection layer. The fact data describes real-time file monitoring and signature-based detection, and nothing else. If you want a firewall or a VPN, you are looking at the wrong app entirely, and no amount of configuration will turn Hypatia into one.

Hypatia does not upload suspicious files to a cloud analysis service. It is designed for offline signature-based scanning, and it does not require an account. The absence of a cloud component is a design property, not a hidden feature you need to disable. Equally, Hypatia is not a privacy optimizer or an ad blocker. It does not clean caches, manage permissions on your behalf, or filter advertising. Those are different product categories that happen to share the word “security.”

Hypatia does not fully replace Google Play Protect, and it cannot detect every type of Android malware. Signature matching catches what has been fingerprinted. Unknown or zero-day samples, and anything that does not present a matching pattern, will pass. A tool with this detection model cannot honestly be described as comprehensive, and the project’s own framing does not claim it is.

Finally, Hypatia is not root-only. Root is not stated as a requirement in the fact data, and the app is distributed through F-Droid as an ordinary installable package. The root myth probably comes from conflating “may not see every file without broad permissions” with “requires elevated privileges,” which are different statements. Check the permissions on F-Droid, but do not assume you need to modify your device to run a scanner.

Coexistence, Conflicts, and Running Hypatia Next to Other Security Apps

Can Hypatia run alongside Google Play Protect without conflicts? The fact data does not describe interaction between the two, so no compatibility statement can be made. What can be observed is that Hypatia requires no account, performs its matching offline, and does not depend on a cloud service — which means the usual sources of conflict between two security products, such as competing cloud lookups or duplicated account integrations, are not described here. That is an absence of a described conflict, not a confirmation that none exists.

The same caution applies to running Hypatia next to another Android antivirus. Nothing in the fact data addresses it. Two scanners both watching files could plausibly duplicate work, but whether Hypatia’s monitoring behaves that way is not documented in the material available. Users who already run a commercial security app and are considering adding Hypatia should treat coexistence as something to verify rather than assume, and should check the project’s GitHub repository for any guidance on the subject.

There is one thing you can do to reduce the risk of surprises: install from the official distribution and keep it updated through the same channel. Hypatia is distributed via F-Droid, and its source lives at Divested-Mobile/Hypatia. Staying on those surfaces means you get the same build the project publishes, with the permissions the listing declares, rather than a repackaged APK from an unknown mirror. For a security tool, provenance is not a detail.

If you do hit something odd — a flag you disagree with, a scan that seems to have missed a file, an unexpected interaction with another app — the repository is where to look first. The fact data does not describe a formal reporting process, so the practical move is to check whether one is documented there before drawing conclusions.

Verdict

Hypatia is worth installing if you are the kind of Android user who wants a free, auditable, offline signature scanner and who understands exactly what that phrase excludes. It matches files and installed apps against known signatures in real time, it is licensed GPL-3.0-only with source on GitHub, it does not require an account, and it is distributed through F-Droid. For a technical user who wants a second, inspectable layer of known-malware detection without a cloud dependency, that is a coherent and defensible package.

It is not worth installing if you want a full antivirus suite. There is no firewall, no VPN, no behavioral analysis, no cloud reputation service, and no web protection. Non-technical users expecting a set-and-forget product backed by a vendor will find nothing here to hold onto, and anyone who expects zero false positives from signature scanning is going to be unhappy — signature matching produces them, and the fact data does not document how they are handled. People on unsupported or very old Android versions should not install it, because no minimum version is stated and compatibility is unverified. iOS users are obviously out of scope. Users who want real-time behavioral blocking of malware are asking for a capability this app does not have.

If you need more than signature matching, the alternatives named in the fact data are commercial apps with broader feature sets: Malwarebytes, which adds scanning and protection features beyond a signature check, and Bitdefender Antivirus Free, a free commercial antivirus for Android. Both come with the tradeoffs that come with commercial software, and neither is a like-for-like swap. The point is not that one is better; it is that Hypatia occupies a narrow position — offline, open source, signature-only — and the right question is whether that position matches your threat model, not whether it beats a full suite at being a full suite.

Pros

  • Open source and auditable
  • Designed for offline signature-based scanning
  • Lightweight real-time scanning approach

Cons

  • Signature-based detection has limited ability to catch unknown or zero-day malware
  • Detection quality depends on signature database freshness
  • Not a full-featured antivirus suite with cloud or behavioral analysis
Download from the official source

The link goes straight to Divested Computing Group. We do not host app files.

Open official page →

Frequently asked questions

Is Hypatia free?

The recorded pricing model is Free.

What license does it use?

It is listed under GPL-3.0-only.

Where can I download the official version?

The official link points to https://gitlab.com/divested-mobile/hypatia.

This article was drafted with AI assistance using official developer documentation, release notes, privacy policies, and public data, then reviewed by an editor. We do not claim lab testing. The full method is on our Review Method page.