Loaded script list (javascripts)
Lists which scripts the page loaded.
In one line
Can list the scripts loaded on its own page
Lists which scripts the page loaded.
A list of script URLs (up to 2,200 chars) can reveal injected scripts from extensions or tools.
What it can and can't do
What the user does: Nothing. It happens when the page loads or when a tool scans the page.
It can
- Find which scripts its page loaded, including ones from other companies
- Spot tracking or ad scripts on its own page
- Check that a script loaded as expected
It cannot
- See scripts on other sites or in other tabs
- See what the scripts do inside other pages
- See your browser add ons unless they change the page
- Keep a list of what you visited before
Browser support
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Supported | Not available | None |
| Edge | Supported | Not available | None |
| Firefox | Supported | Not available | None |
| Safari | Supported | Not available | None |
| Safari on iPhone | Supported | Not available | None |
| Chrome on Android | Supported | Not available | None |
| Samsung Internet | Supported | Not available | None |
How a site asks for it
| API | document.scripts / script elements |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Script reads the value
- Value joins the fingerprint payload
Data you get
What comes back: Loaded script list (javascripts)
Shape: list
How often: per page
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
javascripts | list | None | up to 2200 chars collected | Not listed |
Technical limits
- Only scripts in the DOM
The story
What it is
A site can see which scripts are loaded in the page, which can reveal extensions.
For you
You never see it. A page can tell if some extensions or tools have added their own scripts to it, which says something about how you browse.
For makers
Fraud and security tools use it to spot injected code, bots and shady extensions. It also adds to a device profile used for tracking.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A bank page spots an injected script from malware that tries to steal logins. | Stripe Radar |
| ads | An ad network spots scripts from blockers and tracks how many viewers use them. | None named |
| shopping | A checkout page flags a card skimmer script that was added by an attacker. | None named |
| games | An anti cheat page spots cheat helper scripts running in a browser game. | None named |
| analytics | A tag manager audits which scripts load, to remove slow or unauthorized ones. | Google Tag Manager |
| developer | A developer checks that third party scripts are the ones they approved. | None named |
Risks
- Reveals extensions
- Adds to fingerprint
Good uses and abuse
Legitimate uses
- Detect injected scripts
Known abuse
- Detect extensions that inject scripts
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 2 | Rough identifying entropy, when known |
A real example: LinkedIn
Collector key(s): javascripts. My reading of the key: a list of script sources; the exact field is not described in public write-ups.
Related capabilities
Related
- APFC / DNA device fingerprint (abuse prevention features). Can collect about 48 device traits and send them in secret with later requests
Sources
- mdp/linkedin-extension-fingerprinting (LinkedIn script snapshot and ID list)
- mdp/linkedin-extension-fingerprinting (LinkedIn script snapshot and ID list)
How well checked: Inferred from related behavior.