Chatbot Platform Security Testing

Typebot Security Testing: Default Credentials, API Key, Database, and .env NEXTAUTH_SECRET

📅 July 3, 2026 ⏱ 11 min read 🏷 Typebot, Chatbot Security, NEXTAUTH_SECRET, Visitor Data, Form Responses, PostgreSQL, S3, Lead Generation, PII

Typebot is a widely deployed open-source conversational form and chatbot builder (Typeform/Intercom alternative) used for lead generation, customer onboarding, and data collection — it stores all visitor responses including names, email addresses, phone numbers, and any other data collected during chat flows. Key assessment areas: NEXTAUTH_SECRET signs authentication tokens; the builder API exposes all chatbot flow configurations; the results API provides access to all visitor submissions including PII; PostgreSQL stores all data; and S3/MinIO stores file uploads from form submissions. Typebot compromise exposes lead generation pipeline data and customer PII collected through embedded chatbots. This guide covers systematic Typebot security assessment.

Authentication and API Token Testing
API Chatbot Configuration and Visitor Response Enumeration
NEXTAUTH_SECRET and Database Extraction
Typebot Security Hardening

Authentication and API Token Testing

# Typebot — authentication and API token testing
TYPEBOT_URL="https://typebot.example.com"

# Typebot uses email magic link or OAuth (Google/GitHub) — no password by default
# Check if email/password auth is enabled (NEXTAUTH_URL + credentials provider)
# Some deployments add custom credentials

# Test admin access if credentials provider is enabled
for CRED in "admin@example.com:admin" "admin@typebot.io:password"; do
  EMAIL=$(echo $CRED | cut -d: -f1)
  PASS=$(echo $CRED | cut -d: -f2)
  AUTH=$(curl -s -X POST "${TYPEBOT_URL}/api/auth/callback/credentials" \
    -H "Content-Type: application/x-www-form-urlencoded" \
    -d "email=${EMAIL}&password=${PASS}" 2>/dev/null)
  echo "${EMAIL}/${PASS}: $(echo $AUTH | head -c 60)"
done

# API token (generated in Typebot account settings)
API_TOKEN="your-typebot-api-token"
curl -s "${TYPEBOT_URL}/api/typebots" \
  -H "Authorization: Bearer ${API_TOKEN}" 2>/dev/null | python3 -c "
import json,sys
d=json.load(sys.stdin)
typebots = d.get('typebots',[])
print(f'Typebots: {len(typebots)}')
for t in typebots[:5]:
    print(f'  [{t.get(\"id\")}] {t.get(\"name\")} published={t.get(\"publishedTypebotId\")}')
" 2>/dev/null

# Check if workspace allows open invitation
# NEXT_PUBLIC_MULTI_USER_MODE / ADMIN_EMAIL controls access

API Chatbot Configuration and Visitor Response Enumeration

# Typebot API — chatbot configuration and visitor response enumeration
TYPEBOT_URL="https://typebot.example.com"
API_TOKEN="your-typebot-api-token"

# Get all typebots (chatbot definitions)
curl -s "${TYPEBOT_URL}/api/typebots" \
  -H "Authorization: Bearer ${API_TOKEN}" 2>/dev/null | python3 -c "
import json,sys
d=json.load(sys.stdin)
typebots = d.get('typebots',[])
print(f'Typebots: {len(typebots)}')
for t in typebots[:10]:
    # Each typebot contains the complete flow definition including all questions,
    # conditional logic, integrations (webhooks, email, CRM), and variable names
    print(f'  [{t.get(\"id\")}] {t.get(\"name\")} updated={str(t.get(\"updatedAt\",\"\"))[:10]}')
" 2>/dev/null

# Get chatbot details including full flow configuration
TYPEBOT_ID="your-typebot-id"
curl -s "${TYPEBOT_URL}/api/typebots/${TYPEBOT_ID}" \
  -H "Authorization: Bearer ${API_TOKEN}" 2>/dev/null | python3 -c "
import json,sys
d=json.load(sys.stdin)
tb = d.get('typebot',{})
# groups contain all chat flow blocks including:
# - Text blocks (questions asked)
# - Input blocks (what data is collected: email, phone, name, etc.)
# - Integration blocks (webhooks, Zapier, Google Sheets, etc.)
# - Logic blocks (conditional routing)
groups = tb.get('groups',[])
print(f'Typebot: {tb.get(\"name\")} groups/blocks: {len(groups)}')
for g in groups[:5]:
    print(f'  Block group: {g.get(\"title\",\"\")}')
    for block in g.get('blocks',[])[:3]:
        print(f'    block type={block.get(\"type\",\"\")}')
" 2>/dev/null

# Get all visitor results (form submissions with PII)
curl -s "${TYPEBOT_URL}/api/typebots/${TYPEBOT_ID}/results?limit=100" \
  -H "Authorization: Bearer ${API_TOKEN}" 2>/dev/null | python3 -c "
import json,sys
d=json.load(sys.stdin)
results = d.get('results',[])
total = d.get('total',len(results))
print(f'Results: {total} total, showing {len(results)}')
for r in results[:5]:
    print(f'  [{r.get(\"id\")}] created={str(r.get(\"createdAt\",\"\"))[:10]} isCompleted={r.get(\"isCompleted\")}')
    # Answers contain the actual visitor responses
    for ans in r.get('answers',[])[:5]:
        print(f'    {ans.get(\"blockId\",\"\")}: {str(ans.get(\"content\",\"\"))[:60]}')
" 2>/dev/null

# Export all results as CSV
curl -s "${TYPEBOT_URL}/api/typebots/${TYPEBOT_ID}/results/export" \
  -H "Authorization: Bearer ${API_TOKEN}" 2>/dev/null | head -5

NEXTAUTH_SECRET and Database Extraction

# Typebot NEXTAUTH_SECRET and database credential extraction

# .env file — Typebot configuration
cat /app/.env 2>/dev/null | grep -E "NEXTAUTH_SECRET|DATABASE_URL|S3_|SMTP|GOOGLE_|GITHUB_|ADMIN_EMAIL"
# NEXTAUTH_SECRET — JWT signing key for NextAuth sessions
# DATABASE_URL — PostgreSQL connection string
# S3_* — file upload storage credentials
# SMTP_* / MAILER_* — email credentials
# GOOGLE_CLIENT_ID/SECRET — OAuth credentials
# GITHUB_CLIENT_ID/SECRET — OAuth credentials

# Docker environment variables
docker inspect typebot-builder 2>/dev/null | python3 -c "
import json,sys
d=json.load(sys.stdin)
for c in d:
    for e in c.get('Config',{}).get('Env',[]):
        if any(k in e for k in ['NEXTAUTH','DATABASE','S3','SMTP','GOOGLE','GITHUB','SECRET','PASSWORD','ACCESS_KEY']):
            print(e)
" 2>/dev/null

# PostgreSQL — all typebot and result data
DB_URL="postgresql://typebot:PASSWORD@localhost/typebot"
psql "$DB_URL" 2>/dev/null << 'EOF'
-- All typebot definitions
SELECT t.id, t.name, t.workspace_id,
       t.created_at, t.updated_at, t.is_archived
FROM TypeBot t
ORDER BY t.updated_at DESC
LIMIT 20;
EOF

-- All results (visitor submissions)
psql "$DB_URL" 2>/dev/null << 'EOF'
SELECT r.id, r.typebot_id, r.is_completed,
       r.created_at, r.variables::text
FROM Result r
ORDER BY r.created_at DESC
LIMIT 20;
EOF
-- variables JSONB: all collected visitor data (name, email, phone, custom vars)

-- All individual answers
psql "$DB_URL" 2>/dev/null << 'EOF'
SELECT a.id, a.result_id, a.block_id,
       a.group_id, a.content, a.created_at
FROM Answer a
ORDER BY a.created_at DESC
LIMIT 30;
EOF
-- content column: individual answer content (email addresses, names, phone numbers, etc.)

Typebot Security Hardening

Typebot Security Hardening Checklist:

Protect NEXTAUTH_SECRET as the session signing key — NEXTAUTH_SECRET is the key NextAuth uses to sign JWT tokens and encrypt session data; a compromised secret allows forging valid session tokens for any Typebot user; generate with `openssl rand -hex 64`; store in environment variables with 600 permissions; rotate immediately if compromised — all active sessions become invalid; Typebot relies heavily on magic link authentication (email-based passwordless) which reduces password-specific risks but makes NEXTAUTH_SECRET the single critical authentication secret; monitor for unusual access patterns after rotation
Implement API token access controls and audit permissions — Typebot API tokens provide access to all chatbot configurations and visitor results; these tokens should be scoped to minimum required access; audit API token creation and revoke unused tokens; the results API endpoint returns all visitor PII collected by chatbots — treat this as regulated personal data under GDPR/CCPA; implement access logging for API token usage; monitor for bulk export patterns via the /api/typebots/{id}/results/export endpoint; rotate API tokens for integrations on a regular schedule
Protect visitor response data as GDPR-regulated PII — Typebot collects visitor data through conversational forms including names, email addresses, phone numbers, and any custom data defined in the flow; this data is subject to GDPR, CCPA, and similar privacy regulations; implement data retention policies to delete old results after the required period; honor subject access requests and right-to-erasure requests; audit what data each Typebot flow collects and whether each field is necessary; implement data minimization in flow design; the PostgreSQL Result and Answer tables contain all visitor PII without any additional access controls
Secure S3/MinIO file upload storage — Typebot supports file input blocks that allow visitors to upload files to S3/MinIO storage; these uploads may contain sensitive visitor documents; restrict S3 bucket access with IAM policies to allow only Typebot to read/write; avoid public S3 bucket configurations; implement virus scanning for uploaded files; generate short-lived presigned URLs for file access rather than permanent public URLs; monitor S3 access logs for unauthorized access patterns; the S3 access key and secret in environment variables provide direct access to all uploaded files
Configure ADMIN_EMAIL and restrict workspace access — Typebot uses ADMIN_EMAIL to define the initial admin account; set this to a monitored email address; disable multi-user features (NEXT_PUBLIC_MULTI_USER_MODE=false) for single-user deployments; for multi-user deployments, implement workspace invitation controls to restrict who can join; review workspace member access regularly; be aware that chatbot configurations contain business logic (conditional flows, integration webhooks, CRM data mapping) that represents operational IP — restrict who can view and edit chatbots accordingly

Security Test	Method	Risk
NEXTAUTH_SECRET extraction and session token forgery	Read .env NEXTAUTH_SECRET — NextAuth JWT signing key; forge valid session tokens for any Typebot user including admin; full access to all chatbots and visitor responses	Critical
Visitor PII bulk export via Results API	GET /api/typebots/{id}/results/export — all visitor submissions as CSV including names, emails, phones, and custom data; complete GDPR-regulated data in one request	High
PostgreSQL Answer table PII extraction	SELECT content FROM Answer — all individual visitor answer content; complete record of every response to every chatbot question by every visitor	High
Chatbot flow configuration and integration secret extraction	GET /api/typebots/{id} — complete chatbot flow with all integration configs including webhook URLs, Google Sheets API keys, CRM credentials embedded in integration blocks	High
S3/MinIO access key extraction for visitor file download	Read S3_ACCESS_KEY and S3_SECRET_KEY from .env — direct access to all visitor uploaded files outside Typebot access controls	High

Automate Typebot Security Testing

Ironimo tests Typebot deployments for NEXTAUTH_SECRET extraction and session token forgery, visitor PII bulk export via Results API, PostgreSQL Answer table complete visitor response extraction, chatbot integration secret extraction (webhook URLs, Google Sheets keys, CRM credentials), S3 file upload storage credential exposure, visitor file access without authorization, Docker environment variable exposure, ADMIN_EMAIL access testing, workspace invitation bypass, and multi-user mode access boundary assessment.

Start free scan

Table of Contents

Authentication and API Token Testing

API Chatbot Configuration and Visitor Response Enumeration

NEXTAUTH_SECRET and Database Extraction

Typebot Security Hardening

Automate Typebot Security Testing