Security and privacy decision

Malwarebytes

A basic on-demand scanner is buildable, but reproducing the full Malwarebytes product (real-time multi-OS protection, maintained threat intel, VPN and identity services, and support) requires large proprietary datasets, continuous telemetry, and operational maturity—so keep paying for the commercial product.

Visit website
Subscription$5/month
Initial build80 hours
Monthly upkeep8 hours + $0
Evidence2/3 runs agree

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • A smallest-useful replacement would be an on-demand malware scanner that downloads threat signatures/updates, scans files or paths, and quarantines/removes detected items.

What it still won’t have

  • proprietary threat intelligence and long-term telemetry-backed detection improvements
  • real-time kernel/driver-level protection across OSes
  • integrated VPN, identity monitoring, and insurance features
  • 24/7 vendor support and managed updates

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 2 seats.

Paid seatsseats

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

Time you would spend

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal cross-platform on-demand malware scanner and quarantine manager using: Go for the backend scanner orchestration, ClamAV (or libclamav) for signature-based scanning, SQLite for event/quarantine metadata, and an Electron or React+Flask frontend. In scope: (1) an updater that pulls signature DB updates on a schedule and verifies integrity; (2) a file/path scan API that runs ClamAV scans and returns structured results; (3) quarantine storage (move files to a safe folder) and CRUD for quarantined items in SQLite; (4) a simple UI to start scans, view results, and restore/delete quarantined files; (5) scheduled jobs for periodic update+scan; (6) logging, error handling, and unit tests for the updater, scanner wrapper, and quarantine operations. Out of scope: kernel/driver-level real-time protection, cross-device syncing, VPN/identity features, paid licensing, and managed threat-intel services.
How we checked3 sources · 2/3 runs agreed · evidence score 23

How the score was reached

  • Pay verdict base20
  • 3 cited sources+3
  • Evidence score23

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! Price not confirmed on the page — this pricing page renders its price in the browser! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded