CreepJS and What a Mobile Line Changes

CreepJS is an open-source research project that shows how much a web page can learn about a browser, and in particular how well it can spot a browser that is lying about itself. It reads hundreds of properties, hashes them into fingerprints, looks for contradictions between them and reports traits that suggest headless or automated browsers. It is not a commercial fraud product and no website runs it on you. People still load it through a SpoofProxies line to see what changes. The honest answer is: very little, and understanding why is useful.

What CreepJS is looking at

CreepJS focuses on the browser. It collects values from the navigator object, screen, canvas, WebGL, audio, fonts, CSS media queries, math functions, speech voices, the time zone and more. Then it cross-checks them. If the user agent claims one operating system while the fonts and graphics say another, or if a JavaScript function has been modified in a way that native code would not be, it records a lie. It also reports traits it associates with headless browsers and gives the collected data stable hashes so you can see which parts change between visits.

Almost none of this involves the network. The fingerprints come from your browser and your machine, and they would be identical on home Wi-Fi, office Ethernet or a carrier line.

The few places the line appears

CreepJS does show some connection-related data. It can display the addresses seen through WebRTC and it reports the browser's time zone and locale, which it may compare against the network location. Through a carrier line you want WebRTC to expose nothing outside the proxy, and you want the time zone and locale to match the line's metro. Those two points are configuration on your side. Our lines give a true AT&T, T-Mobile or Verizon route in the metro you picked; aligning the browser with it is a matter of setting the right region.

If CreepJS shows a time zone contradiction, fix the profile's time zone. That is the whole remedy, and it is the same thing a real person would have if their laptop clock matched where they were.

Reading lies and headless traits

A result full of lies usually means a browser whose properties have been changed by an extension or tool. A result with headless traits usually means automation. Neither is something a proxy creates or removes, and we do not provide or recommend ways to hide them. For honest work, such as QA automation on your own sites, headless traits are expected and harmless; your own site should be configured to allow your test traffic. For managing real accounts by hand, the least modified browser is the one with the fewest contradictions.

It is also worth remembering what CreepJS is. It is an intentionally strict research tool. A trait it reports may be something few production sites weigh at all, and a result it calls suspicious does not mean any specific platform agrees.

Why a clean network does not fix a noisy browser

People sometimes hope that a trusted mobile address will outweigh a browser that contradicts itself. Platforms do not work that way. They collect network and device signals separately, and a contradiction in one is not cancelled by good news in the other. Carrier-grade NAT means a carrier address is shared by many people, which is why platforms lean on device and behaviour to tell them apart. That makes the browser half more important on mobile networks, not less. CreepJS is a clear way to see that half without a platform's opinion mixed in.

Using it for your own QA

Developers building fingerprinting or bot defences for their own products use CreepJS to understand which signals are stable and which are noisy. Pairing it with a line in each metro lets them confirm that their location and time zone logic handles real mobile users sensibly. That is a good use of both tools, and a dedicated line keeps the network side constant while you change the browser side.

Setting up a CreepJS proxy on SpoofProxies

1. Add a line in the metro you want and copy its credentials.
2. Set the test browser's time zone and locale to that metro.
3. Configure the browser to use the line over HTTP or SOCKS5.
4. Load CreepJS and check the WebRTC and time zone sections first.
5. Compare the fingerprint hashes with a run on your normal connection to see which values stayed the same.
6. Treat lies and headless traits as browser questions, separate from the network.

CreepJS proxy questions