Account Consistency from Gameplay Traces: Same-Player Verification in Counter-Strike 2

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2608.24893v2 Announce Type: replace Abstract: In competitive first-person shooter (FPS) games such as Counter-Strike 2 (CS2), account-integrity review often asks whether an account's recent behavior remains consistent with its historical operator. This consistency question arises in cases such as temporary substitution, rank boosting, and high-skill players using lower-ranked accounts, where manual review requires comparing a current match against multiple historical matches. We formulate this review task as same-player verification: we encode the behavioral trajectory of a single player in a match replay (demo) as a demo-player behavioral fingerprint, and train a model to judge whether two behavioral observations come from the same real player. Using CS2-specific domain knowledge, the fingerprints cover crosshair control, movement-stop-fire coordination, economy/buy, combat/engagement, and temporal rhythm. We construct strict six-fold evaluations on the Perfect dataset (3,570 demos and 35,700 demo-player observations) and the Professional dataset (539 demos and 5,390 demo-player observations). The final pairwise model reaches ROC AUCs of 0.926 and 0.956, respectively. Feature analysis shows that the strongest identity signals come from aiming/crosshair and other low-level mechanical behaviors, indicating that stable mechanics are more informative for this verification task than single-match performance outcomes. On fixed eligible query cohorts, aggregating pairwise evidence between a current demo and multiple historical demos raises account-history AUC on Perfect …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2608.24893
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.