Delhi Police have arrested a 14-year-old accused of breaching careerprogression.mha.gov.in. The Ministry of Home Affairs (MHA) runs this portal to help former Agniveers move into jobs with the Central Armed Police Forces (CAPFs), Assam Rifles, state police forces and private security agencies licensed under PSARA. ThePrint broke the story in English and Hindi, citing unnamed official sources. It reports that the accused listed "verified admin credentials" for the portal on a dark web marketplace, along with access to more than 2,500 ex-Agniveer personnel records across 47 government departments. Every account of the incident so far traces back to ThePrint's reporting. Delhi Police have not issued a public statement and the MHA has not commented. Nobody has independently confirmed what the seller claimed to have, so this brief treats those claims as advertised rather than verified.
What Happened
ThePrint reports that a specialised Delhi Police unit spotted the listing in September 2026 while monitoring dark web marketplaces. An official source told the outlet that the team "noticed that an account claimed to sell verified admin credentials for the MHA Agniveer recruitment portal." Police traced the account to the boy and detained him "within days," according to the same reporting. The arrest only became public on 20 November, roughly two months later.
Some points remain unclear:
- Was data actually sold? ThePrint's English headline says the records were "listed" for sale. The Hindi version's headline says they were "sold" (बेचे). Neither version says a buyer paid or received any data. That gap matters for assessing the harm.
- How long did the attacker have access? No timeline has been published covering when the portal was first breached, how long admin access lasted, or whether anyone else used the same weakness.
- What happens legally? Because the accused is a minor, the case will probably go through juvenile justice proceedings. No charges or sections of the IT Act have been reported.
What Was Taken
Everything below comes from the seller's listing as two officials described it to ThePrint. The government has not confirmed any of it.
- Personnel records: "2500+ agniveer personnel records across 47 government departments." ThePrint's English and Hindi reports both give this figure, and no other count has been reported. The data fields in these records have not been disclosed. A careers portal for ex-servicemembers typically holds names, contact details, service history and job applications.
- Admin panel access: full control of user management, organisation management, police station data, reports, grievances, job applications, letters, and import and export functions.
- Infrastructure secrets: an "API decryption key for all traffic," single sign-on (SSO) integration details, a "complete backend route map," and "ready to use scripts."
The infrastructure items are probably more serious than the record count. If the listing was accurate, the SSO details could expose identity systems the portal shares with other government services, and the API key would let a buyer decrypt the portal's traffic. A buyer would then have long-term access to the hiring pipeline that links former soldiers to police and paramilitary forces, which is more valuable than a one-time copy of the data.
Why It Matters
This is the latest in a run of Indian public-sector and critical-sector security incidents this autumn. In most of them, the organisation that was breached did not detect the problem itself:
- State Bank of India: A group calling itself "Siriusim" claimed to have stolen about 3.75 lakh (375,000) records. Accounts of how many customer records were in that data differ. SBI's 21 October stock-exchange filing, as summarised by the Internet Freedom Foundation, identified 3,897 customer records containing personal data. The police FIR, as reported by The Economic Times citing the Times of India, refers to 4,280 customer records, around 32 CSV files and 2,721 PDFs. SBI found out from outside alerts, including from CERT-In and the Defence Cyber Agency, after the data had already been published.
- eMudhra: Private keys for eight intermediate certificate authority certificates were compromised: six TLS certificates and two code-signing certificates. The Hindu reports that some keys were trivially small numbers, one of them simply 4. An anonymous researcher discovered the flaw, not the company. MeitY set up a special investigation team.
- Ministry of Road Transport and Highways: The ministry asked CERT-In for a forensic audit of its VAHAN, SARATHI, e-Challan and PUCC portals. This followed an investigation by the security firm Cyderes, which found vehicle-owner data on sale through Telegram channels and mobile apps for as little as ₹5.
The ex-Agniveer case is a partial exception: law enforcement found the listing by actively monitoring the dark web, so outside parties did not have to alert anyone. Even so, the portal's owner does not appear to have detected the intrusion. And if the reported age is correct, a 14-year-old reached a government admin panel with enough access to advertise SSO details and decryption keys. That points to basic security weaknesses rather than an advanced attacker.
Under CERT-In's 2022 Directions, organisations must report cyber incidents within six hours and keep logs for 180 days. India's Digital Personal Data Protection Act, 2023 will require organisations to protect personal data and report breaches once it is fully enforced, which is expected in 2027. Nothing published so far shows whether the affected ex-Agniveers have been, or will be, notified.
The Attack Technique
The intrusion method has not been disclosed. ThePrint reports only that the minor "had identified vulnerabilities" on the portal. Based on what the listing advertised, some possibilities are worth considering, though none is confirmed:
- Exposed or weak admin login: The advertised "verified admin credentials" suggest the attacker took over or created an admin account. Weak passwords, reused passwords or a login page without rate limiting could each explain this.
- Secrets on the client side or in source code: An "API decryption key for all traffic" and a "complete backend route map" are the kind of material found in exposed JavaScript bundles, debug endpoints, misconfigured storage or leaked repositories.
- Broken access control: A full map of backend routes plus ready-made scripts suggests the attacker listed and tested API endpoints. One likely weakness is IDOR (insecure direct object reference), where the server lets a user fetch other users' records by changing an ID without checking permissions.
The government has not confirmed whether the vulnerability has been fixed, whether the SSO secrets and API keys have been rotated, or whether a forensic review is under way.
What Organizations Should Do
- Rotate every secret the listing names. If any credential, API key or SSO secret was advertised for sale, assume it is compromised, whatever happened after the seller's arrest. Rotate SSO client secrets, signing keys and service credentials for every system that trusts the portal, not just the portal itself.
- Require phishing-resistant multi-factor authentication on all admin panels and keep them off the public internet. Put admin interfaces behind a VPN, zero-trust access gateway or IP allowlist. A citizen-facing careers site does not need its user-management console reachable from anywhere.
- Keep cryptographic keys out of client code. Run automated scans of front-end bundles and code repositories for embedded keys and route maps. Encrypt traffic with TLS and keep keys on the server. The eMudhra incident is a reminder to check key strength as well.
- Check access control on every API route. Test for IDOR and missing authorisation checks, especially on bulk import and export endpoints, which can expose whole datasets in one request.
- Monitor dark web marketplaces for your own domains. Here, police monitoring detected the listing. In the SBI case, outsiders raised the alarm. Organisations that run sensitive portals should pay for their own monitoring of brokers that sell access, so they do not depend on others to notice.
- Meet reporting and notification deadlines. Report to CERT-In within six hours of detection, keep the 180 days of logs that investigators will need, and tell affected people what was exposed. Notifying investors or regulators alone is not enough.
Sources: Exclusive: Teen held for 'hacking' MHA ex-Agniveer career portal | Road Ministry seeks forensic audit of its portals after vehicle dat... | Eight web security keys of eMudhra firm used by Govt. and PSUs leak... | SBI data breach: FIR filed a month after hackers steal 3.75 lakh re... | Exclusive: अग्निवीर पोर्टल हैक कर 2,500 से ज्यादा रिकॉर्ड डार्क वेब... | Unknown gaps: India must do better at detecting and preventing data... | eMudhra breach: IT ministry says digital signature & eSign services... | SBI has told the stock exchanges about its data breach, but not the...