Skip to main content

Research & Case Studies

Case studies

Real problems, how they were investigated, what was done and what the evidence shows, including what it does not show.

How to read the evidence labels
Client work
Based on a delivered client engagement, published with the client's permission.
Client work, anonymised
Based on a delivered client engagement. Identifying details are withheld.
Internal implementation
Based on systems PrajnaBytes built and runs itself. Not a client deployment.
Demonstration project
A demonstration or prototype built to test an approach. Not a client deployment.
Experimental research
Results from controlled tests. They may not hold in other environments.
Independent research
Research from publicly available evidence. The organisations discussed were not PrajnaBytes clients.
Desk research
Based on the cited public sources, with PrajnaBytes' interpretation marked as such.
1 result in Content Security PolicyClear

Results

Case studyIndependent research17 min read

AIIMS Delhi Website Ad Injection: A Historical Third-Party JavaScript Case Study

In December 2022 a visitor-counter script on the official AIIMS Delhi website was found to be placing third-party advertising at the top of the page. This case study reconstructs what happened from the original report and from archived copies of the script, separates verified facts from interpretation, and sets out what the episode teaches about third-party JavaScript.

  • Third-party JavaScript
  • Web security
  • Supply-chain risk
  • Content Security Policy

Facing a similar problem?

Tell us what you are dealing with. We will say honestly whether we can help, and how.

Talk to us
+91 99116 64994support@prajnabytes.com