Skip to main content
Incident intelligence/SS-IR-059CASE FILE OPEN
Symbolic editorial illustration for SS-IR-059SERVANTSTACK // INCIDENT INTELLIGENCEFORENSIC IMAGE // VERIFIED FRAME
SS-IR-059 // INCIDENT REPORTDocumented

McDonald's

AI Hiring Bot 'Olivia' Left 64 Million Applicant Records One '123456' Login Away

EXECUTIVE BRIEF

McDonald's runs its hiring through McHire, a recruitment platform built by Paradox.ai and fronted by an AI chatbot named "Olivia" that screens job applicants.

FAILURE CHAINTRACE COMPLETE
  1. 01TRIGGERMcDonald's runs its hiring through McHire, a recruitment platform built by Paradox.ai and fronted by an AI chatbot…
  2. 02MACHINE ACTIONAutonomous actor
  3. 03MISSING GATENamed SME review and decision audit trail
  4. 04IMPACTData security
01 // INCIDENT SUMMARY

The short version

McDonald's runs its hiring through McHire, a recruitment platform built by Paradox.ai and fronted by an AI chatbot named "Olivia" that screens job applicants.

02 // KEY FACTS

Case telemetry

INCIDENT
SS-IR-059
DATE
June 30, 2025
SYSTEM
McDonald's
LOCATION / SCOPE
Global (McDonald's McHire platform, US-based Paradox.ai)
EVIDENCE
Documented
AI ROLE
Autonomous actor
HARM
Data security
SOURCES
2 cited records
03ENTRY POINT // WHAT HAPPENED

The event

McDonald's runs its hiring through McHire, a recruitment platform built by Paradox.ai and fronted by an AI chatbot named "Olivia" that screens job applicants. On June 30, 2025, security researchers Ian Carroll and Sam Curry disclosed that they logged into the McHire administrative backend using the username "123456" and the password "123456" -- default test credentials left active on an account that still had access to live production data. Once inside, they found an Insecure Direct Object Reference (IDOR) flaw in an internal API: by simply decrementing the numeric applicant ID in a request, they could pull any applicant's full record. The exposed data included names, email addresses, phone numbers, full Olivia chat transcripts, shift preferences, personality-test results, and authentication tokens. The maximum applicant ID showed roughly 64 million applicant records were reachable this way. The researchers responsibly viewed only seven records (five containing real PII) to prove the flaw. Paradox.ai acknowledged it within about an hour and disabled the default credentials and secured the endpoint by July 1, 2025.

04CAUSAL TRACE // AI'S ACTUAL ROLE

What the machine did

The Olivia chatbot was the data-collection front end: it conducted automated applicant conversations and harvested personal data, shift preferences, and personality-test answers into a backend with no enforced access control on the records it created. The AI hiring pipeline was deployed at national scale with no human security review gate over its administrative access model -- a test account with the password "123456" and full live-data reach was allowed to ship to production, and no human validated that the API enforced authorization per record. The system collected tens of millions of people's data at machine speed while the human controls that should have gated it were simply absent.

Autonomous actorAutomation was a causal participant—not a decorative label for the system around it.
05BLAST RADIUS // CONSEQUENCES

Where the failure landed

Up to approximately 64 million job-applicant records were exposed and reachable by anyone who guessed the trivial default credentials. The data spanned names, contact details, complete AI chat transcripts, and screening results -- a high-value target for phishing, recruitment scams, and identity fraud against people applying for entry-level jobs. Although the researchers limited their own access to seven records and the flaw was patched within roughly a day, the window during which the data sat behind a "123456" password is unknown, and the incident became a global case study in AI-deployment security failure, drawing coverage and a national-security-grade embarrassment for both McDonald's and Paradox.ai.

06 // EVIDENCE STATUS

Documented

Supported by a first-party disclosure, technical research, or corroborated reporting cited below.

SOURCE RECORD UPDATED 2026-07-09

07 // SOURCE LEDGER

2 cited records

  1. 01
  2. 02
08CONTROL FAILURE // MISSING GOVERNANCE

Named SME review and decision audit trail

The failure pattern in this case: Automated judgment without accountable review.

09INTERVENTION POINT // HUMAN IN THE MIDDLE

The moment the path could change

A qualified reviewer tests the basis, context, and disparate impact before the decision reaches a person.

AI PROPOSESHUMAN OWNS THE DECISIONSYSTEM EXECUTES
10CONTROL DEPLOYMENT // AUTHORITYGATE

SME routing · decision audit trail

AuthorityGate's Operational Resilience framework requires a human SME change-validation gate before any AI-facing system handling personal data is promoted to production. A security SME would have run the standardized pre-deployment access-control checklist that this release skipped: (1) verify no default or test credentials (no "123456" account) retain access to live data, and (2) confirm every data-returning API enforces per-record authorization, blocking the exact IDOR pattern where decrementing an ID returns someone else's record. Under the framework, the human reviewer must sign off that authentication AND authorization both pass against the production data store -- and that the AI chatbot's collected records inherit those controls -- before the deployment is released. The McHire launch could not have cleared that gate with a "123456" admin login and an unauthenticated record-enumeration endpoint, so the exposure would have been caught and remediated before a single applicant's data went live.

DIRECT AUTHORITYGATE ANALYSISMcHire Exposed 64 Million ApplicantsThe full analysis of default credentials, broken record authorization, and automated collection at national scale.
12 // THE ALTERNATIVE

Autonomy is a design choice.

See the operating model that keeps AI useful while preserving human authority at consequential moments.

Compare AgenticAI and AugmentedAI →