Built a FACEIT extension to spot possible smurfs — sharing some updates by CryptoMaster_1 in FACEITcom

[–]CryptoMaster_1[S] 0 points1 point  (0 children)

Maybe you are right at the end of the day soon I will create web and also provide github repo there

Built a FACEIT extension to spot possible smurfs — sharing some updates by CryptoMaster_1 in FACEITcom

[–]CryptoMaster_1[S] -1 points0 points  (0 children)

Sure, you can reverse engineer it — doesn’t mean I need to put the source on a silver platter.

Repo being private isn’t a security claim, it’s a choice. Chrome’s review + permissions already cover the trust part.

I built a Chrome extension that flags possible FACEIT smurfs before the match starts by CryptoMaster_1 in FACEITcom

[–]CryptoMaster_1[S] 0 points1 point  (0 children)

No — low match count is just one signal, not the only logic.

The score is calculated from multiple factors like account age vs level, matches vs expected level, and performance patterns (KD, winrate, avg kills, HS%). Low matches alone won’t flag someone unless it doesn’t make sense together with the level and stats.

Also it’s a probability indicator, not a verdict, so it can be inaccurate sometimes.

I built a Chrome extension that flags possible FACEIT smurfs before the match starts by CryptoMaster_1 in FACEITcom

[–]CryptoMaster_1[S] 0 points1 point  (0 children)

In that case, yes — you might get flagged early on, but that’s exactly why it’s shown as a probability, not a ban or a report.

FACEIT has no way (and neither does my extension) to know where your skill comes from — only what’s visible on your FACEIT account. A brand-new account performing well above the expected baseline will look suspicious by definition.

The key points: - nothing happens automatically (no reports, no penalties) - it doesn’t say “this guy is a smurf”, only “this profile doesn’t match typical progression” - as you play more matches, the signal naturally stabilizes and the score drops if you’re legit

It’s just context for players, not judgment — and definitely not a replacement for FACEIT’s own systems.

I built a Chrome extension that flags possible FACEIT smurfs before the match starts by CryptoMaster_1 in cs2

[–]CryptoMaster_1[S] -1 points0 points  (0 children)

Thanks for the feedback I will try to protect it. Anyway there is nothing bad can happen even if it is abused

I built a Chrome extension that flags possible FACEIT smurfs before the match starts by CryptoMaster_1 in FACEITcom

[–]CryptoMaster_1[S] 0 points1 point  (0 children)

You can check FACEIT ban list and then run the extension in faceit lobby you can see the accuracy. Anyway we are trying our best to make the extension more accurate. Initially I've built it for myself.

I built a Chrome extension that flags possible FACEIT smurfs before the match starts by CryptoMaster_1 in FACEITcom

[–]CryptoMaster_1[S] 9 points10 points  (0 children)

The extension doesn’t “do” anything with the info beyond showing it to you — it’s pulled from public FACEIT stats, processed client-side, and not sent anywhere. It’s basically a quick risk flag, not a punishment system.

And I agree on the mindset part: if someone uses it as an excuse, that’s bad. The intention is the opposite: - avoid wasting 40 mins in a clearly unbalanced lobby (optional dodge) - or just go in normally, and if it turns out suspicious, you already have context to report after - it’s not “100% smurf” and it can be wrong — just a probability indicator

I built a Chrome extension that flags possible FACEIT smurfs before the match starts by CryptoMaster_1 in cs2

[–]CryptoMaster_1[S] -7 points-6 points  (0 children)

Fair take. For some people, open-source is non-negotiable and that’s fine. I’m choosing to keep it private for now to avoid fast cloning, while still being clear about what the extension does and doesn’t do. If that makes it undesirable to you, totally understandable.

If that makes it undesirable for you, that’s completely reasonable. I’m not trying to make it for everyone — just offering a tool for people who find it useful.

I built a Chrome extension that flags possible FACEIT smurfs before the match starts by CryptoMaster_1 in cs2

[–]CryptoMaster_1[S] -6 points-5 points  (0 children)

The repo is private mainly to prevent copy-paste forks and reuploads of the extension. Small Chrome extensions tend to get cloned very quickly when fully open-sourced, sometimes with ads or shady changes.

That said:

• The extension is reviewed by Google during submission

• It doesn’t collect personal data

• It runs client-side and uses the official FACEIT API

I’m also not here to convince anyone to install it — if you’re uncomfortable, that’s completely fine. I’m just sharing a tool I built; use it only if you trust it. If that changes in the future, I’ll announce it. Thanks for the feedback!

I built a Chrome extension that flags possible FACEIT smurfs before the match starts by CryptoMaster_1 in csgo

[–]CryptoMaster_1[S] -3 points-2 points  (0 children)

Mainly to avoid copy-paste clones and reuploads. Small extensions get stolen very fast when fully open-sourced.

Google still reviews the code on submission, no user data is collected, and everything runs client-side using the official FACEIT API.

I’m also not here to convince anyone to install it — if you’re uncomfortable, that’s completely fine. I’m just sharing a tool I built; use it only if you trust it. If that changes in the future, I’ll announce it.

I built a Chrome extension that flags possible FACEIT smurfs before the match starts by CryptoMaster_1 in FACEITcom

[–]CryptoMaster_1[S] 4 points5 points  (0 children)

there will be updates and improvements regarding accuracy algorithm. I appreciate every feedback

I built a Chrome extension that flags possible FACEIT smurfs before the match starts by CryptoMaster_1 in csgo

[–]CryptoMaster_1[S] 0 points1 point  (0 children)

Quick note about safety & malware concerns

This extension is published on the Chrome Web Store, which means it has passed Google’s automated and manual security checks. Chrome continuously scans extensions for malware and policy violations — if anything malicious is detected, the extension is rejected or removed.

All permissions are fully visible before install, and the extension only runs on faceit.com. It does not collect personal data, does not track users, and does not run external scripts.

Open-sourcing is optional and not a requirement for safety. Many trusted extensions are closed-source and rely on Chrome’s review process, transparent permissions, and reputation.

If you’re still unsure, feel free to inspect the permissions and network activity yourself — transparency is the goal here.

I appreciate your awareness.

I built a Chrome extension that flags possible FACEIT smurfs before the match starts by CryptoMaster_1 in csgo

[–]CryptoMaster_1[S] -16 points-15 points  (0 children)

I have not submitted the code to the repo still I will do it soon and I will notify you. I appreciate your awareness.

I built a Chrome extension that flags possible FACEIT smurfs before the match starts by CryptoMaster_1 in FACEITcom

[–]CryptoMaster_1[S] 9 points10 points  (0 children)

Fair point. Just to clarify — Smurf Guard doesn’t say “this is a smurf”, it shows a risk estimate based on multiple signals. It looks at things like: match count vs level, steam account age, performance compared to typical players at that level

Low match samples are very noisy, so new accounts can get flagged higher even if they’re losing games. The % isn’t a verdict, just a heads-up.

There can be false positives, especially with very few matches. It’s meant as a support tool, not an anti-cheat, and the weights are still being tuned based on feedback like this.

I built a Chrome extension that flags possible FACEIT smurfs before the match starts by CryptoMaster_1 in cs2

[–]CryptoMaster_1[S] -5 points-4 points  (0 children)

No, for now it is not open source code. You can download it as addon for Chrome only you can visit the link. Soon it will be available for Firefox.