thepumptheftauto.fun
“Pump Theft Auto · Rob them before they rob you”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
Wallet connection
“…efore GTA VI comes out Playfree · in your browser · no wallet connect Name Solana address · where you get paid Play The pot…”E20
No matching code, calls or services in what loaded for us.
What it is
- The Internet Archive has never saved this site, so it is probably new.E21
- The site describes itself as: “A whole crime city in your browser. Take any car, hold up stores, take the cash off anyone carrying it, bank it for SOL. $PTA”E2
- Notable building blocks in its code: Three.js (3D graphics).E8
- In your browser it can copy text to your clipboard, saves small bits of data in your browser, keeps a live two-way connection open to a server and runs compiled WebAssembly code in your browser.E9E10E11E12
- It has sections such as /docs.E19
- While loading, it called 1 endpoint on its own servers, such as /api/clientlog.E15
Where your data goes
Analytics & trackingCount visits and record what you do on the page. 1
| static.cloudflareinsights.com | Cloudflare Web Analytics: page-view counter | 1×E6 |
How key features work
Sign-in and accounts
Sign-in and account features show up in its code or traffic (/api/account).E18
/api/accountLive updates
It keeps live connections open (WebSockets) so content updates without reloading.E11
websocketLoading its content
Its content loads from its own API while you browse (/api/clientlog).E15
/api/clientlogDrawing and editing in the browser
The page draws and edits graphics in your browser using Three.js (3D graphics), WebAssembly and the canvas.E8E12E14
Three.js (3D graphics)webassemblycanvasMeasuring what you do
Visits and clicks are measured with Cloudflare Web Analytics (found in its traffic or its code).E6
Cloudflare Web AnalyticsCookies and storage
Names only. We never store the values.
localStorageE7: stickup.pid
Pages and API calls
Evidence
Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.
Limits
- We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
- Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
- Some trackers only load after you accept cookies or log in, so the real list can be longer.
- We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
- The tech check compares the site's own words with what its public page loads. Work done on servers, in private code or in separate apps isn't visible here, so 'nothing found' means not visible on the public page, not that it doesn't exist.
- This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
- The code reader hit its size budget on parts of 47 large bundle file(s); those parts weren't fully analysed.
Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id RnUpiNeH.