PreMatch for FACEIT: Opponent Stats, Smurf Check, Map Veto extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: cnmfemloeoohjicgpjcdolklcejfnkjg
Permissions (4)
- Execute scripts in pages
Related extensions
Faceit-ExtenderProductivity
FACEIT Vision - 2D/3D Replay, ELO Stats, Roles, Map Predictor, Auto-AcceptProductivity
Faceit ToolkitLifestyle
FACEIT GRIND: Win Chance, Faceit Rating, Smurf Checker, Roles, Auto-AcceptProductivity
Pregame - FACEIT CS2 Predictor, Veto & ScoutLifestyle
Prefire for FACEIT - Auto Accept, Stats & Win ChanceLifestyle
Frequently asked questions
Is PreMatch for FACEIT: Opponent Stats, Smurf Check, Map Veto safe to use?
Our latest automated scan rates the Chrome listing of PreMatch for FACEIT: Opponent Stats, Smurf Check, Map Veto at 78/100 (some risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does PreMatch for FACEIT: Opponent Stats, Smurf Check, Map Veto require?
PreMatch for FACEIT: Opponent Stats, Smurf Check, Map Veto requests 4 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops PreMatch for FACEIT: Opponent Stats, Smurf Check, Map Veto?
PreMatch for FACEIT: Opponent Stats, Smurf Check, Map Veto is published by PreMatch Team. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 2.0.3
- Current listed version
- 2.0.3
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 critical and 5 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.