Skip to main content
Blog
Blog

A new Progressive Web App danger very few know about

The rise in adoption with PWAs comes an increase in client-side security risks. And the industry? It’s barely talking about it.

Dec 20, 2024 2 min read
new-pwa-danger-image-cover

Progressive Web Apps (PWAs) have revolutionized how we build and deliver applications. It’s no wonder they’ve gained traction. They simplify development, combining the flexibility of the web with the capabilities of mobile. Features like offline access, push notifications, and hardware integration ... all wrapped in the convenience of a browser. With updates like those in iOS 16.4 in 2023, embedding browser capabilities into apps is easier than ever, driving the new wave of PWA adoption.

But there’s a flipside. With their rise comes an increase in client-side security risks. And the industry? It’s barely talked about.

Screenshot showing Tinder as a Progressive Web App
The Tinder app is a PWA.

PWAs are browsers

At their core, PWAs are browsers. They transform every app into a micro-web environment. That’s their power—they load instantly, reuse website code, and connect to web services seamlessly. Yet, this very architecture also exposes them to the web’s vulnerabilities, especially client-side risks tied to 3rd-party scripts.

Modern websites depend on these scripts for everything from analytics to engagement tools. While convenient, they massively expand your attack surface. In a PWA, these same scripts run directly in the app, amplifying risks like data breaches, malicious injections, and more.

Your risk isn’t limited to website visitors anymore; it extends to every app user.

Keep the web supply chain in mind

The client-side is the final stop in the chain. It’s where your code, both 1st and 3rd-party, loads into the user’s browser or PWA.

3rd-party scripts sourced from external vendors are integral but often fall outside your control, making them prime targets for attackers. From compromised analytics scripts leaking user data to malicious code injected into chatbots, the client-side is under constant threat.

Building a PWA only amplifies these risks by bringing them into your app.

PWAs are not bad

With all this being said, we don’t advocate against using PWAs. Depending on your needs, they’re likely the smartest choice. Just don’t overlook the security challenges they bring. Unfortunately, client-side vulnerabilities, especially from 3rd-party scripts, are often ignored.

We’ve built cside, a 3rd-party script monitoring and security tool. This solves all these problems in both web and PWA environments. Install it right now, or talk to us - we’re more than happy to help you get started.

Simon Wijckmans
Founder & CEO

Founder and CEO of cside. Previously a product manager on Cloudflare Page Shield (now Cloudflare Client-Side Security). Co-chair of the W3C Anti-Fraud Community Group and a Forbes 30 Under 30 honoree. Building accessible security against client-side attacks — web security is not an enterprise-only problem.

FAQ

Frequently Asked Questions

Progressive Web Apps can be installed silently and request capabilities that look like a native app. Once installed, a malicious PWA can deliver push notifications, run in the background, and impersonate trusted brands far more convincingly than a normal web page.

Monitor the third-party scripts on your site so an attacker cannot inject a manifest or service-worker registration. cside flags new script and worker behavior on the client, which is the only layer where this risk is visible.

Monitor and Secure Your Third-Party Scripts

Gain full visibility and control over every script delivered to your users to enhance site security and performance.

Start free, or try Business with a 14-day trial.

cside dashboard interface showing script monitoring and security analytics
Related Articles
Book a demo