CYBERRAKSHAK LABS Β· RESEARCH #049

🚨 Alleged CAG India Website Compromise β€” Database, Admin Panel & Web Shell Offered for Sale

CyberRakshakLabs analyzes an alleged dark-web claim involving cag.gov.in, an apparent CAG administrative interface, and claims of database and web-shell access; compromise scope remains independently unverified.

By Vivek Kumar Β· Published 2 October 2026
RESEARCH#049
CATEGORYThreat Intelligence / Web Security / Government Infrastructure
CRL ASSESSMENTHIGH
RESEARCH LEVELDeep Research
PUBLISHED2026-10-02
Source & social links:
LinkedIn Post β†—WhatsApp β†—YouTube β†—
How CyberRakshakLabs researches threats β†’
The listing may be real. The full compromise is not yet proven. A newly observed dark-web claim alleges compromise of CAG's public web infrastructure and offers database, administrative-panel and web-shell access for $300. The available evidence supports treating this as a serious validation lead, while keeping database theft and web-shell access explicitly unverified.
$300Claimed sale price
~140Historical CAG subsite context
MEDIUMConfidence in successful compromise
Important: This research analyses a threat-intelligence listing and the supplied evidence. The listing itself is a high-confidence observation, but successful database exfiltration, web-shell installation, root/server access and full CAG infrastructure compromise remain unverified.
1. Executive Summary

A newly observed dark-web listing claims that an attacker compromised the Comptroller and Auditor General of India (CAG) website and is offering database access, administrative panel access and a web shell for sale.

The listing was recorded as discovered on 2026-10-02 02:24:05 UTC and claims that a weakness in cag.gov.in was exploited. The supplied screenshots appear to show CAG-related website content, attacker-controlled content and an administrative interface associated with Accountant General (A&E), Mizoram, Aizawl.

The screenshots do not independently prove complete database theft, persistent web-shell access, unrestricted administrative control, root/server access or compromise of the wider CAG infrastructure.

CyberRakshakLabs assessment: A credible threat-intelligence lead that warrants immediate validation, but it should not yet be publicly labelled as a confirmed CAG data breach.
2. What the Screenshot Shows

The first supplied screenshot is a threat-intelligence listing titled β€œAlleged hack of Comptroller and Auditor General of India with database, admin panel and web shell offered for sale”. The listing identifies cag.gov.in as the target, claims exploitation of a weakness, lists a database, admin panel and web shell as alleged assets, and shows a claimed price of $300.

The listing records a discovery timestamp of 2026-10-02T02:24:05.000Z, approximately 07:54 AM IST on 2 October 2026.

The second screenshot appears to show CAG website content with an attacker-controlled overlay and an administrative interface. It also appears to reference Accountant General (A&E), Mizoram, Aizawl, and a URL structure containing /admin.

3. What the Evidence Does β€” and Does Not β€” Prove
CAG website content→Apparent admin interface→Threat-actor claim→Independent validation required

The evidence supports documenting the existence of the claim and examining the apparent administrative access. It does not independently establish database contents, database exfiltration, web-shell execution, persistence, root access, access to all CAG subsites, employee credentials, audit records outside the affected application, or modification/destruction of official records.

4. CAG's Existing Web Architecture β€” Historical Attack-Surface Context

CAG's public documentation describes a large website environment with approximately 140 subsites and a CMS used for content management and administrative access. The supplied material describes an older stack including RHEL 7.1, Apache 2.4.6, PHP 7.2.24, MySQL 5.6.38 and CakePHP 3, and notes that the documented technology was considered outdated and subject to upgrade requirements.

This historical documentation does not prove that the 2026 incident resulted from the old stack. It does, however, establish why investigators should examine the full CMS and subsite architecture rather than only the public homepage.

~140 subsites→Central / distributed CMS→Administrative interfaces→Multiple user roles→Large attack surface
5. Current Status of the Official Website

During the supplied verification, cag.gov.in was reachable and serving normal website content, including expected CAG sections and 2026 material. The site being operational does not by itself invalidate the dark-web claim.

Possible explanations include temporary access, access to a specific administrative subsystem or subsite, file upload followed by loss of access, modification that was subsequently reversed, or fabricated evidence. Therefore, β€œwebsite currently online” is not equivalent to β€œno compromise”.

6. Three Levels of the Claim

Level 1 β€” Website compromise

The screenshot appears to show attacker-controlled content on CAG-related website infrastructure. Status: potentially credible, but independently unverified.

Level 2 β€” Administrative access

The screenshot appears to show an administrative panel. Status: stronger indicator, but validation is required to establish that it came from an authenticated session.

Level 3 β€” Database + Web Shell

The actor claims both are for sale. Status: unverified.

Key distinction

A screenshot can be evidence of a claim without proving the complete compromise scope.

7. Possible Attack Chain β€” Investigation Hypothesis

Based on the available evidence, a hypothetical chain could be:

Internet-facing CAG application→Initial weakness→Application compromise→Authentication / session bypass→Administrative access→File upload / code execution→Web shell→Database access→Data collection→Persistence→Dark-web sale

Only the middle portion is supported by the attacker’s claim. The initial vulnerability and exact exploitation mechanism remain unknown.

8. Possible Initial Access Vectors

A. Public-facing application vulnerability

Internet β†’ vulnerable CMS/application β†’ unauthorized access.

B. Authentication weakness

Credential compromise β†’ admin login β†’ CMS access.

C. Session/authentication bypass

Application weakness β†’ authentication bypass β†’ admin panel.

D. File upload vulnerability

Unauthenticated/authenticated upload β†’ PHP/web shell β†’ remote execution.

E. Compromised administrative account

Credential theft β†’ valid login β†’ admin panel β†’ possible web shell/data access.

Investigation rule

None of these should be selected as the actual attack vector without forensic evidence.

9. Web Shell Claim β€” Why It Matters

If the web-shell claim is genuine, the incident would be materially more serious than a simple defacement. A PHP web shell could potentially provide command execution, file-system access, credential discovery, database access, persistence and deployment of additional payloads, depending on server permissions.

Investigators should examine application configuration and secret stores for database credentials, API keys, SMTP credentials, application secrets, encryption keys and session secrets. These are potential capabilities, not confirmed actions in this incident.

Command execution→File-system access→Credential discovery→Database access→Persistence→Additional payloads
10. Database Exposure Risk

If the database claim is genuine, investigators should determine exactly which database was accessed and what data, if any, was exfiltrated. Possible categories include CMS users, administrative accounts, user metadata, audit-related content, website content, application configuration, contact information, internal administrative records and session information.

Public wording should avoid saying β€œCAG’s entire database was leaked.” A defensible formulation is: β€œA threat actor claims to have obtained and is offering a CAG database for sale; the authenticity, scope and provenance of the alleged database have not been independently verified.”
11. DFIR Review of the Screenshot

The second screenshot should be examined as a digital-forensics lead. Investigators should extract the exact URL, timestamp, displayed user/session context, office context and visible administrative functions.

βœ“ Exact administrative URL
βœ“ Screenshot timestamp
βœ“ Displayed user/session
βœ“ Accountant General (A&E), Mizoram, Aizawl
βœ“ Complaint/Suggestion
βœ“ Notices
βœ“ Accounts
βœ“ Training
βœ“ Circulars / Office Orders
βœ“ Banner management
βœ“ Other CMS functions

The visible functions suggest the interface may be part of a content/administrative management system rather than necessarily the central CAG infrastructure. That distinction requires investigation.

12. CAG's Existing Cybersecurity Documentation

The supplied material notes that CAG public documentation includes cybersecurity guidance, data and network security information, cyber-incident reporting guidance, KAVACH references and security-related SOPs. A CAG circular regarding NIC access instructs officials to use KAVACH for two-factor authentication for NIC-hosted email and applications and references reporting cyber incidents to CERT-In within the applicable reporting window.

This context shows that cybersecurity procedures are documented; it does not establish whether those controls were involved in or bypassed during the alleged incident.

13. MITRE ATT&CK Mapping β€” Potential Techniques Only
Technique IDTechniqueRelevance
T1190Exploit Public-Facing ApplicationPossible initial access
T1078Valid AccountsPossible if admin credentials were compromised
T1133External Remote ServicesPossible depending on access mechanism
T1505.003Web ShellRelevant if web shell is genuine
T1005Data from Local SystemPossible if server/database data was collected
T1119Automated CollectionPossible if bulk extraction occurred
T1567Exfiltration Over Web ServicePossible if stolen data was transferred externally
T1098Account ManipulationPossible if admin accounts were created or modified
None of these techniques should currently be presented as confirmed attacker behaviour. They are investigation hypotheses requiring forensic validation.
14. IOC / Evidence Table
IndicatorValueStatus
Target domaincag.gov.inConfirmed target in listing
Listing discovery2026-10-02 02:24:05 UTCScreenshot/listing evidence
Claimed price$300Threat-actor claim
Claimed databaseYesUnverified
Claimed admin panelYesScreenshot-supported claim
Claimed web shellYesUnverified
Alleged attacker handle0x4zir / similarScreenshot-derived; preserve exact original evidence
Proof screenshotHosted under CAG domain, according to listingRequires independent validation
Admin URL / panelVisible in screenshotScreenshot-derived
Official domaincag.gov.inOfficial domain

The attacker's Telegram contact information should not be republished in the public CyberRakshakLabs article.

15. Evidence Confidence Matrix

Dark-web listing exists

High β€” supplied screenshot

Listing targets CAG

High

Listing appeared on 2 Oct 2026

High

Actor claims database access

High β€” claim only

Actor claims web-shell access

High β€” claim only

Screenshot shows CAG-related admin interface

Medium–High

Successful admin compromise

Medium / requires validation

Actual database exfiltration

Low / unverified

Web shell actually installed

Low / unverified

Root cause

Unknown

Attacker identity

Unknown

Data publicly leaked

Not established

Full CAG infrastructure compromised

Not established

16. What CAG / Incident Responders Should Check Immediately

If the claim has not already been investigated, the highest-value forensic checks are:

Web server

  • Access logs
  • Error logs
  • PHP logs
  • WAF logs
  • Reverse-proxy logs
  • File creation timestamps
  • Recently modified PHP files
  • Uploaded files
  • Unexpected *.php, *.phtml, *.php5 and *.phar files under /uploads/, /webroot/ and /admin/

CMS

  • Admin login logs
  • Failed login attempts
  • Session creation
  • Password resets
  • New administrator accounts
  • Privilege changes
  • Plugin/module changes
  • CMS configuration changes

Database

  • New users
  • Privilege changes
  • Suspicious SQL queries
  • Bulk SELECT activity
  • Database exports
  • Unexpected tables
  • Modified application configuration
  • Credential changes

Web shell hunting

  • eval(
  • base64_decode(
  • gzinflate(
  • gzdecode(
  • shell_exec(
  • system(
  • passthru(
  • proc_open(
  • popen(
  • assert(

Network

  • Outbound connections from web servers
  • Unusual destinations
  • Large outbound transfers
  • Database connections
  • Command-and-control indicators
  • DNS anomalies

Searching for dangerous PHP functions alone is not sufficient because legitimate applications may contain some of them. Investigators should correlate file location, timestamps, code structure and execution logs.

17. Critical DFIR Question
The most important question is not β€œDid someone hack cag.gov.in?” It is: β€œHow did the attacker move from the public-facing application to the administrative interface, and did that access reach the database or server operating system?”

A useful investigation chain is:

Initial Access→Application Compromise→Authentication→Admin Panel→Code Execution?→Web Shell?→Database Access?→Data Exfiltration?→Persistence?

Every arrow needs evidence.

18. CyberRakshakLabs Assessment

This is a credible threat-intelligence lead that warrants immediate validation, but it should not yet be labelled publicly as a confirmed CAG data breach.

The most interesting element is the apparent combination of website content, an administrative interface, a claimed web shell and a claimed database. If independently validated, that would represent a materially more serious compromise than ordinary website defacement.

However, the current evidence primarily consists of a threat-actor marketplace claim and screenshots. The official CAG website was reported as accessible and serving normal content, while CAG documentation provides historical context about a large multi-subsite CMS architecture and an older documented technology stack.

Observation β‰  Validation β‰  Attribution. A screenshot showing apparent access is evidence of a claim β€” not automatically proof of the full compromise scope.

Recommended CyberRakshakLabs Headline

CAG.gov.in Under Alleged Attack: Database, Admin Panel and Web Shell Offered for $300

Subtitle: A newly observed dark-web listing claims compromise of India’s Comptroller and Auditor General website. Screenshots suggest access to a CAG administrative interface, but database theft and web-shell access remain independently unverified.

πŸ”΄ The listing is real. The compromise claim requires validation.