Is BetterFloat safe?
BetterFloat injects a page-level fetch/XHR interceptor into 26 skin-trading marketplaces and sends pro users' Steam IDs to its own server.
On the CS skin marketplaces it supports, BetterFloat runs a hook in the page's own JavaScript context that captures every API response the site loads, including authenticated account, inventory, and order data, and re-broadcasts the full response bodies as page-level events that any script on that site can read. For pro/VIP-tier users, the extension also attaches the user's 64-bit Steam ID to an x-steamid header on each price lookup sent to api.betterfloat.com, linking the Steam account to marketplace activity. Free users send an empty Steam ID and the interceptor only re-exposes data within the same site origin.
Who publishes itRums - 1 other listing from the same operator, none carrying a finding
Rums - 1 other listing from the same operator, none carrying a finding
What this publisher told the store about itself, and the other listings that told it the same thing.
Same store account
1 other listing published from this account, 6k+ users between them, none of them carrying a finding.
Shared hosts - 2 hostnames
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Where it sends data
Destinations our analysis observed BetterFloat contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- api.betterfloat.com
BetterFloat sends data to api.betterfloat.com. No other extension we have analyzed sends data here.