InfoCode
How to fix: Service Worker Registration
Service worker registration detected.
Why it matters
Compromised SW can intercept all requests.
Service workers are powerful and persistent.
How to fix it
- 1Ensure SW is properly secured and scoped.
Code examples
Restrict Service Worker scope + add CSP
// Register with minimal scope
navigator.serviceWorker.register("/sw.js", { scope: "/app/" });
// In the Service Worker, validate response integrity:
self.addEventListener("fetch", (event) => {
// Only intercept same-origin requests
const url = new URL(event.request.url);
if (url.origin !== self.location.origin) return;
event.respondWith(caches.match(event.request) || fetch(event.request));
});References
Detected automatically by VulnRadar. The check id is service-worker-insecure, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is Service Worker Registration?
- VulnRadar rates this info severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id service-worker-insecure, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.