SDK: Node.js

Suspicious login detection for Node.js

Add suspicious login detection to any Node.js authentication flow.

Install command

npm install loginllama@^3.1.0

Add LoginLlama to Node.js in one call

Call LoginLlama from your Node.js 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.

Node.js login check
import { LoginLlama } from 'loginllama';

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

// Use middleware for automatic IP/User-Agent detection
app.use(loginllama.middleware());

// Pre + Post Auth Pattern - Most complete protection
app.post('/login', async (req, res) => {
  const { email, password } = req.body;

  try {
    // Step 1: Pre-auth check (before verifying credentials)
    const preCheck = await loginllama.check(email, {
      authenticationOutcome: 'pending'  // Mark as pre-auth check
    });

    // Block high-risk attempts before authentication
    if (preCheck.risk_score > 7) {
      return res.status(403).json({ error: 'Login blocked' });
    }

    // Step 2: Authenticate with your system
    const authResult = await authenticate(email, password);

    // Step 3: Report outcome to LoginLlama
    if (authResult.success) {
      await loginllama.reportSuccess(authResult.user.id);
      return res.json({ success: true });
    } else {
      // Report failed auth - helps detect brute force attacks
      await loginllama.reportFailure(email);
      return res.status(401).json({ error: 'Invalid credentials' });
    }
  } catch (error) {
    console.error('LoginLlama error:', error);
    return res.json({ success: true }); // Fail open on errors
  }
});

Why teams choose LoginLlama for Node.js

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 Node.js stack

ExpressNext.js API routesNestJSFastify

Node.js login security FAQ

How do I add suspicious login detection to Node.js?

Install LoginLlama with `npm install loginllama@^3.1.0`, then call the risk check from your Node.js 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 Node.js logins?

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

What does LoginLlama detect on Node.js 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 Express, Next.js API routes, NestJS, Fastify?

Yes. LoginLlama runs at the login step itself, so it works alongside Express, Next.js API routes, NestJS, Fastify and the rest of your Node.js stack without replacing your existing authentication provider.

Other integrations

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

Node.js login protection

Protect Node.js users from suspicious logins

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

Start with 100 free checks