On-device · Explainable · Privacy-first

See through fake login windows.

界 Kai watches the live page for credential-harvesting UI — overlay phishing, cross-origin login forms, browser-in-the-browser spoofs and seed-phrase prompts — and tells you exactly why, before you type.

🔒 Detection runs 100% on your device. No page content ever leaves your browser.
Suspicious login window detected BLOCKED · RISK 11
  • Browser-in-the-browser spoof — fake window chrome (V3)
  • Brand mismatch — "Microsoft" on secure-login.cc (O1)
  • Cross-origin form — posts to login-collect.cc (S1)
⛔ Submission blocked — do not enter credentials.
100%
On-device detection
Zero
Page content sent
Every
Verdict is explained
You
Decide who to trust
Threat coverage

What 界 Kai catches

No single signal decides — 界 Kai weighs many, relative to the page's own origin and your trust store, so the combination is what raises a flag.

Browser-in-the-browser

Fake "OS browser window" drawn in HTML to spoof an OAuth popup. 界 Kai spots the painted chrome.

V3 · window-chrome spoof

Cross-origin credential form

A login form that posts your password to a foreign origin — judged relative to the page you're actually on.

S1 · cross-origin post

Overlay phishing

An injected modal or overlay collecting credentials on top of a legit-looking page.

gate · password field

Seed-phrase prompts

A uniform recovery-phrase input grid, or recovery-phrase wording — a hallmark of wallet-draining sites.

W1 · C1 · seed grid

Brand impersonation

A known brand's name or mark on a non-matching, lookalike or freshly-registered domain.

O1 · brand mismatch

Submission interception

On a block verdict, 界 Kai arms the form and stops the submit, so credentials never leave — not even on a misclick.

stage 4 · block + action
Layered & explainable

A pipeline, not a black box

Every stage runs locally and contributes reasons. The on-device AI only adjudicates borderline cases — it can never force trust.

STAGE 0

Gate

Is there a password field or seed-phrase wording? If not, stop. This is the main false-positive control.

STAGE 1

Heuristics

Weighted rule catalog scores the page and emits a stable id + human reason for each signal.

STAGE 2

Reputation

A signed, per-domain modifier from your own trust store and optional local feeds.

STAGE 3

Local AI

Borderline only: Gemini Nano on-device gives a bounded, advisory verdict. Never commits trust.

STAGE 4

Decision

Map the final score to inform / warn / block, attach actions, and explain every reason.

In-page notice · 御札

It tells you why — in plain words

A calm paper notice, two severities. It informs or warns; on a block, it intercepts the submission.

Possible credential phishing WARN · RISK 6
  • Seed-phrase input grid — 12 uniform cells (W1)
  • Recovery-phrase wording detected (C1)
Warn — flagged, not blocked.
Suspicious login window detected BLOCKED · RISK 11
  • Browser-in-the-browser spoof (V3)
  • Brand mismatch — "Microsoft" on secure-login.cc (O1)
  • Cross-origin form — posts to login-collect.cc (S1)
⛔ Submission blocked — do not enter credentials.
Block — submission intercepted.
Privacy by design

Everything stays on your device

界 Kai inspects the page in your browser. No domain, no page content, and no credential ever leaves it.

100% on-device detection

All scoring and decisions run locally and work offline. Nothing is uploaded by default.

No page content sent

界 Kai reads structure, not your data. It never transmits what you type or what a page contains.

On-device AI, bounded

The optional Gemini Nano adjudicator runs in your browser, only on borderline cases, and only advises.

You are sovereign over trust

Your allowlist and per-site decisions outrank built-in lists, feeds, heuristics and the AI.

Questions

Will it block my real logins?

No. Nothing is scored unless a password field or seed-phrase wording is present, and reasoning is relative to the page's own origin. Trusted providers are allowlisted out of the box, and your own allowlist always wins — so legitimate logins stay quiet.

What is credential-harvesting UI?

Phishing that lives in the page: overlay login modals, fake "browser windows" (browser-in-the-browser), forms that post your password to another origin, brand impersonation, and seed-phrase prompts that drain crypto wallets.

Does it send my data anywhere?

No. Detection is 100% on-device and works offline. No domain or page content is sent to any server by default; the optional AI adjudicator also runs locally via Chrome's built-in model.

Which browsers are supported?

Chromium-based browsers like Chrome, Edge and Brave. The on-device AI step uses Chrome's built-in Prompt API (Gemini Nano) where available, and is skipped gracefully when it isn't.

Free, on-device, and explainable.

界 Kai stands guard at the login. Install once — it watches every page and explains every call.

Add to Chrome — free

* Pending store review; you can load it via developer mode in the meantime. See the project docs.