Skip to content

Developer Sought on a Breach Forum to Build a Mexican KYC Bot Capturing ID Scans and Face Biometrics

Recruitment Watch Mexico flagMexico Telecom / Identity Verification Hiring Post

Developer Sought on a Breach Forum to Build a Mexican KYC Bot Capturing ID Scans and Face Biometrics

A member posting as Cookiegen131 is recruiting a developer to build a Telegram based identity verification system for a stated Mexican telecom project. The specified flow collects front and back images of the INE national identity card, runs OCR validation, then opens a live camera session for liveness checking and face comparison against the document, before passing the result to a telecom registration workflow. The request is technically ordinary and the post carries an unusually explicit instruction against deepfakes, spoofing or anything designed to defeat a verification provider. Nothing in the specification is inherently illegitimate. The venue, and what the finished system would accumulate, are why it is worth noting.

MarketMexico
DocumentsINE front and back
BiometricsLiveness, face match
PosterCookiegen131

Post details

TypeDeveloper recruitment
CountryMexico flagMexico
Stated purposeTelecom KYC registration
Front endTelegram bot plus web step
Deliverables14 components listed
TermsNDA offered, budget unstated
Observed
PosterCookiegen131, 7 posts

!Specified components

  • Telegram bot front end
  • INE front and back capture
  • OCR document validation
  • Real time camera session
  • Liveness verification
  • Document to face comparison
  • Secure document storage
  • KYC state machine
  • PostgreSQL schema
  • Admin verification dashboard
  • Logging and audit system
  • Encryption at rest
  • Docker deployment
  • Sandbox with test identities

Screenshots

Why it matters

Whatever the intent, the finished system would accumulate a KYC grade identity set on every Mexican citizen who passes through it: both faces of the national identity card, the parsed data behind it, and a live face capture proving the person was present. That combination is precisely what account opening and SIM registration checks are built to demand, so whoever controls the resulting database controls the means to pass those checks. The delivery route compounds it, because an end user has no way to distinguish a legitimate Telegram identity bot from a harvesting one, and the same architecture serves both without a line of code changing. Mexican context matters too: the country's mandatory biometric SIM registry was struck down as unconstitutional in 2022, so a telecom flow requiring biometric capture invites questions about the legal basis being relied on.

iAssessment

Unverified

Two readings fit the evidence and neither can be settled from the post. Taken at face value, this is a straightforward contracting request, and the specification argues for it: the explicit prohibition on synthetic media and bypass mechanisms, the insistence on genuine capture, and a sandbox built on fictional identities are not what someone building a harvesting funnel would normally write down. Against that, a lawful telecom project has ordinary hiring channels available, and recruiting on a forum devoted to breached data is a choice that needs explaining. No operator, budget or client is named, and the account is small and recent. Dark Web Informer is not reproducing the contact handle, and notes that no compromise of any Mexican carrier or identity system is claimed or implied here.

Want everything on this listing? Paid subscribers get the full claim details and more. Check out the threat feed, then after subscribing, search there for this alert. View pricing →

DARK WEB INFORMER - THREAT INTELLIGENCE

Latest