How to fix: Script Loaded From a Development Tunnel Domain
A <script> tag loads code from a development tunneling domain (ngrok, localtunnel, Cloudflare Tunnel trycloudflare.com, or serveo.net).
Why it matters
Dev tunnels are ephemeral, unauthenticated by default, and not designed to serve production traffic; if the tunnel expires or is reassigned, the script reference can start resolving to someone else's tunnel entirely, a supply-chain takeover with zero effort required from the attacker.
Developer tunneling tools are meant for temporarily exposing a local dev server for testing (webhooks, mobile device testing, demos). A production page referencing one almost always means a temporary URL was pasted in during development and never replaced with the real deployed asset URL.
How to fix it
- 1Replace the tunnel URL with the script's real, permanently-hosted production URL.
- 2Add a CI check that fails the build if any bundled/rendered output references a known tunneling domain.
- 3Rotate/kill the exposed tunnel once confirmed unnecessary.
Code examples
Use the real deployed asset URL
<!-- BAD -->
<script src="https://a1b2c3d4.ngrok-free.app/bundle.js"></script>
<!-- GOOD -->
<script src="https://cdn.example.com/bundle.js"></script>References
Detected automatically by VulnRadar. The check id is cs-dev-tunnel-script-reference, stable across every scan so you can filter or diff on it.
More client-side checks
- HighCSP Allows 'unsafe-inline' Scripts
- MediumCSP Allows 'unsafe-eval'
- HighpostMessage Without Origin Validation
- HighSensitive Data Stored in localStorage
- HighDOM XSS via location.hash Assignment
- Highdocument.write() in Page Scripts
- Higheval() in Client-Side JavaScript
- MediumExternal Script Without Subresource Integrity
Questions
- How severe is Script Loaded From a Development Tunnel Domain?
- VulnRadar rates this high severity in the client-side 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 cs-dev-tunnel-script-reference, 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.