QueuePal – Auto Accept, Map Veto & Elo for KarasuCS 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: oighnkalicdkkinpfapaoiciegjfbncj
Permissions (4)
- Store local data
- Text-to-speech
- Create offscreen documents
Related extensions
Faceit EnhancedGames Entertainment
Eloboss.net x Faceit Pre-Match Checker (Map & Server)Lifestyle
Faceit ToolkitLifestyle
EloPeek: CS2 Match Room Stats & Map VetoProductivity
CSRun for FACEIT — CS2 Map Veto, Elo & League Team StatsProductivity
Prefire for FACEIT - Auto Accept, Stats & Win ChanceLifestyle
Frequently asked questions
Is QueuePal – Auto Accept, Map Veto & Elo for KarasuCS safe to use?
Our latest automated scan rates the Chrome listing of QueuePal – Auto Accept, Map Veto & Elo for KarasuCS at 92/100 (low 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 QueuePal – Auto Accept, Map Veto & Elo for KarasuCS require?
QueuePal – Auto Accept, Map Veto & Elo for KarasuCS requests 4 permissions. The most significant: Store local data, Text-to-speech, Create offscreen documents. See the full breakdown in the security report.
Who develops QueuePal – Auto Accept, Map Veto & Elo for KarasuCS?
QueuePal – Auto Accept, Map Veto & Elo for KarasuCS is published by raduselea@gmail.com. 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.2.4
- Current listed version
- 2.2.4
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 0 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.