Lucia Identity Provider Integration

Lucia Auth Suspicious Login Detection

Add a risk check to a Lucia-style login handler, between the password check and createSession.

Install command

npm install loginllama

Add LoginLlama to Lucia in one call

Call LoginLlama from your Lucia login handler before you create the session. Send the email, IP, and user agent, then allow, challenge, or block based on the returned risk score.

Lucia login check
// Install: npm install loginllama
// A login handler built the way the Lucia guide describes
import { LoginLlama } from 'loginllama';
import { createSession, generateSessionToken } from './session';
import { verifyPassword } from './users'; // your own user lookup

const loginllama = new LoginLlama({
  apiKey: process.env.LOGINLLAMA_API_KEY!
});

export async function POST(request: Request) {
  const form = await request.formData();
  const email = String(form.get('email'));
  const user = await verifyPassword(email, String(form.get('password')));
  if (!user) return new Response('Invalid credentials', { status: 401 });

  // Score the login before the session row exists. Fail open: an
  // outage lets the sign-in through.
  const result = await loginllama
    .check(email, { request })
    .catch(() => null);
  if (result && result.risk_score > 7) {
    return new Response('Sign-in blocked', { status: 403 });
  }

  const token = generateSessionToken();
  await createSession(token, user.id);
  // Set the session cookie with the token, as in the Lucia guide.
  return new Response(null, { status: 302, headers: { Location: '/' } });
}

Why teams choose LoginLlama for Lucia

Score every login in under 100ms

Detect VPNs, proxies, and TOR exit nodes

Explain why a login is risky with clear risk reasons

Catch errors from the check and logins go ahead during an outage

How it works

Step 1

Install or connect LoginLlama

Choose the SDK or integration point that fits your auth flow and add your API key.

Step 2

Check risk at login time

Send the email, IP, and device context before completing authentication.

Step 3

Act on the risk score

Allow, challenge, or block the login based on risk score and reasons.

Signals we analyze

New device or browser fingerprints

Impossible travel and velocity checks

Bot-like login bursts and credential stuffing

Geo anomalies and risky IP reputation

Works well with your Lucia stack

OsloDrizzleSvelteKitNext.jsAstro

Lucia login security FAQ

How do I add suspicious login detection to Lucia?

Install LoginLlama with `npm install loginllama`, then call the risk check from your Lucia login handler before you create the session. Send the user's email, IP address, and user agent, and branch on the returned risk score.

Will LoginLlama slow down Lucia logins?

No. Risk scoring returns in under 100ms. If LoginLlama is unreachable the check throws an error, so catch it and let the Lucia login go ahead. An outage then never blocks a real user.

What does LoginLlama detect on Lucia logins?

New devices and browser fingerprints, impossible travel and login velocity, credential-stuffing bursts, and traffic from VPNs, proxies, TOR exit nodes, and high-risk IPs — each returned with a clear, human-readable reason code.

Does LoginLlama work with Oslo, Drizzle, SvelteKit, Next.js, Astro?

Yes. LoginLlama runs at the login step itself, so it works alongside Oslo, Drizzle, SvelteKit, Next.js, Astro and the rest of your Lucia stack without replacing your existing authentication provider.

Other integrations

LoginLlama works with the same single API call across every stack.

Lucia login protection

Protect Lucia users from suspicious logins

Add LoginLlama in minutes and block risky logins in real time.

Start Free