Report Suspected Algorithmic Cheating or Hardware Exploitation

1. Match Identification & Competitor Profiles - Essential match context and competitor identification details

Provide complete match identification and competitor profile information to establish the foundation of this incident report. All fields marked mandatory must be completed before submission.

 

Tournament Name

Event Name

Unique Match ID

Game Title

Game Version/Build Number

Server Region

 

Specify other server region:

Match Phase

 

Additional pressure level notes for semifinal:

 

Additional pressure level notes for grand final:

Match Format

Current Score/Match State When Incident Occurred

Incident First Detected Timestamp (Local Event Time)

Competing Teams Information

Team Name

Organization

Team ID

Seed/Rank

A
B
C
D
1
Alpha Strikers
TechCorp Gaming
TEAM-001
3
2
Beta Defenders
Elite Sports Org
TEAM-008
5
3
 
 
 
 
4
 
 
 
 
5
 
 
 
 
6
 
 
 
 
7
 
 
 
 
8
 
 
 
 
9
 
 
 
 
10
 
 
 
 

Suspected Player(s) Information - List all players under suspicion with primary suspect marked

Primary Suspect

In-Game Name

Real Name

Player ID

Seat Number

Team Name

Role/Position

A
B
C
D
E
F
G
1
ShadowSnipe
Alex Chen
PLAYER-492
3
Alpha Strikers
AWPer
2
RapidFire
Maria Rodriguez
PLAYER-501
4
Alpha Strikers
Entry Fragger
3
 
 
 
 
 
 
4
 
 
 
 
 
 
5
 
 
 
 
 
 
6
 
 
 
 
 
 
7
 
 
 
 
 
 
8
 
 
 
 
 
 
9
 
 
 
 
 
 
10
 
 
 
 
 
 

On-Site Referee(s) Information - Identify all referees present and primary investigator

Primary Investigator

Referee ID

Full Name

Certification Level

Contact Email

A
B
C
D
E
1
REF-2847
Jordan Smith
Level 3 - Senior
j.smith@tournament.org
2
REF-3156
Taylor Lee
Level 2 - Advanced
t.lee@tournament.org
3
 
 
 
 
4
 
 
 
 
5
 
 
 
 
6
 
 
 
 
7
 
 
 
 
8
 
 
 
 
9
 
 
 
 
10
 
 
 
 

2. Flagged Anomaly & Server Log Data - Detailed anomaly classification and technical detection evidence

Document the specific nature of the detected anomaly with precise technical details, server logs, and detection evidence. This section forms the core of the technical investigation.

 

Primary Violation Category (select all that apply)

 

Aim Assistance Subtype

 

Vision Assistance Subtype

 

Describe the input automation pattern observed:

 

Modified Peripheral Type

 

Network Manipulation Method

 

Describe the unauthorized device and its suspected function:

 

Describe the game file tampering method:

 

Describe the other technical violation in detail:

Initial Detection Source

 

Anti-Cheat System Name and Version:

 

Describe the visual cues or behavioral patterns observed:

 

Reporting Player/Team Name:

 

Reporting Coach/Manager Name:

 

Spectator Credential ID:

 

Monitoring System Name:

 

Replay Analysis Conducted Timestamp:

Did the official anti-cheat system generate any alerts or flags?

 

Anti-Cheat Alert Details

Alert Timestamp

Alert Code/ID

Alert Severity

Alert Description

Confidence Score (%)

A
B
C
D
E
1
7/15/2025, 2:32 PM
AC-2025-8847
CRITICAL
Inhuman reaction time detected - 50ms flick with 100% accuracy
98
2
7/15/2025, 2:35 PM
AC-2025-8848
HIGH
Consistent pre-firing pattern without visual information
87
3
 
 
 
 
 
4
 
 
 
 
 
5
 
 
 
 
 
6
 
 
 
 
 
7
 
 
 
 
 
8
 
 
 
 
 
9
 
 
 
 
 
10
 
 
 
 
 

First Anomaly Detection Timestamp (Precise)

Anomaly Duration Observed (seconds)

Server Log Entries - Extract relevant log entries surrounding the incident

Log Timestamp

Log Level

Event Type

Player ID

Event Description

Source IP/Identifier

A
B
C
D
E
F
1
7/15/2025, 2:32 PM
INFO
Player Connect
PLAYER-492
Player ShadowSnipe connected from client
192.168.45.103
2
7/15/2025, 2:32 PM
WARN
Anomaly Detected
PLAYER-492
Input pattern deviation exceeds threshold - 4.2 sigma
192.168.45.103
3
7/15/2025, 2:32 PM
DEBUG
Input Analysis
PLAYER-492
Mouse trajectory: linear interpolation detected
192.168.45.103
4
 
 
 
 
 
 
5
 
 
 
 
 
 
6
 
 
 
 
 
 
7
 
 
 
 
 
 
8
 
 
 
 
 
 
9
 
 
 
 
 
 
10
 
 
 
 
 
 

Game Replay Timestamp References - Mark all relevant moments

 

Specify other timestamps and descriptions:

Behavioral Analysis Confidence Assessment - Rate confidence level for each observed behavior

No Evidence

Low Confidence

Medium Confidence

High Confidence

Certain

Inhuman reaction time (<100ms) with high accuracy

Pre-firing without visual/audio cues

Perfect crosshair placement tracking through walls

Impossible flick shots with mechanical precision

Consistent no-scope accuracy beyond human capability

Unnatural movement patterns or pathing

Instantaneous target switching with zero overshoot

Repeated identical input patterns (bot-like behavior)

Automated Detection Confidence Score (if available)

Manual Observation Notes and Detailed Description of Anomalies

Upload Supporting Video Evidence (replay clips, screen recordings)

Choose a file or drop it here
 

Upload Screenshot Evidence (frame-by-frame analysis, visual overlays)

Choose a file or drop it here

3. Hardware Inspection & Network Capture Analysis - Physical and network forensic examination results

Document all hardware inspection findings and network forensic analysis. This section captures physical evidence examination that may support or refute the software anomaly claims.

 

Was immediate hardware inspection conducted on suspect's equipment?

 

Hardware Inspection Start Timestamp:

 

Explain why hardware inspection was not conducted:

Hardware Devices Inspected (select all that were examined)

Were any unauthorized or modified hardware devices detected?

 

Unauthorized Hardware Details

Device Type

Manufacturer

Model/Serial

Modification Description

Suspected Function

A
B
C
D
E
1
Gaming Mouse
CompTech
CT-X9000-SN8847
Additional memory module detected in firmware
Macro storage and execution
2
 
 
 
 
 
3
 
 
 
 
 
4
 
 
 
 
 
5
 
 
 
 
 
6
 
 
 
 
 
7
 
 
 
 
 
8
 
 
 
 
 
9
 
 
 
 
 
10
 
 
 
 
 

Peripheral Device Inspection Results - Document each inspected device

Device Type

Manufacturer

Model Number

Firmware Version

Inspection Status

Notes/Findings

A
B
C
D
E
F
1
Gaming Mouse
CompTech
CT-X9000
FW-v2.1.4
Flagged
Unofficial firmware detected
2
Gaming Keyboard
KeyMaster
KM-Pro
FW-v1.8.2
Cleared
Standard firmware verified
3
Competition PC
TournamentPC
TPC-Comp-2025
BIOS-v5.3
Cleared
No unauthorized software found
4
 
 
 
 
 
 
5
 
 
 
 
 
 
6
 
 
 
 
 
 
7
 
 
 
 
 
 
8
 
 
 
 
 
 
9
 
 
 
 
 
 
10
 
 
 
 
 
 

Was network traffic capture and analysis performed?

 

Network Capture File Reference ID:

Network Anomalies Detected (select all observed)

Network Latency Analysis - Document ping and packet loss during incident

Measurement Timestamp

Player ID

Ping (ms)

Packet Loss (%)

Jitter (ms)

Game Event

A
B
C
D
E
F
1
7/15/2025, 2:32 PM
PLAYER-492
12
0
2
Normal play
2
7/15/2025, 2:32 PM
PLAYER-492
85
12
45
Suspect kill
3
7/15/2025, 2:32 PM
PLAYER-492
15
0
3
Post-incident
4
 
 
 
 
 
 
5
 
 
 
 
 
 
6
 
 
 
 
 
 
7
 
 
 
 
 
 
8
 
 
 
 
 
 
9
 
 
 
 
 
 
10
 
 
 
 
 
 

Upload Running Processes List from suspect's machine during match

Choose a file or drop it here
 

Firmware Version Anomalies or Software Discrepancies Found

Was any physical tampering or modification evident on devices?

 

Describe physical modifications observed:

Upload Hardware Forensic Image or Dump File (if seized)

Choose a file or drop it here
 

4. Player Statement & Immediate Referee Action - Player testimony and immediate tournament response documentation

Document all player statements, witness accounts, and immediate actions taken by tournament officials. This section captures the human element and immediate response protocol.

 

Was formal player interview conducted before match conclusion?

 

Interview Conducted Timestamp:

 

Explain why no interview was conducted:

Player Admission Status

 

Document player's admission statement:

 

Document player's explanation:

 

Document player's denial statement:

Complete Player Statement (if obtained)

Witness Statements from Other Officials

Witness Name

Witness Role

Contact Information

Statement Summary

Credibility Score

A
B
C
D
E
1
Taylor Lee
Referee
t.lee@tournament.org
Observed same flick shot pattern but was not primary observer
 
2
Chris Park
Observer
c.park@tournament.org
Camera angle showed no visible targets before flick
 
3
 
 
 
 
 
4
 
 
 
 
 
5
 
 
 
 
 
6
 
 
 
 
 
7
 
 
 
 
 
8
 
 
 
 
 
9
 
 
 
 
 
10
 
 
 
 
 

Immediate Action Taken by Referee

Match Status Decision

Evidence Preservation Steps Taken (select all applied)

Was Tournament Director notified immediately?

Upload Communication Log (email, chat, voice recording transcripts)

Choose a file or drop it here
 

Suspect Player Signature (if interviewed and statement provided)

Primary Referee Signature (attesting to accuracy of report)

5. Esports Integrity Commission Sign-Off - Final adjudication and sanction determination

Final review and adjudication by the Esports Integrity Commission. This section requires official commission member review and determination of sanctions based on all evidence presented.

 

Commission Review Session Timestamp

Final Violation Determination

Severity Classification

Recommended Sanctions (select all applicable)

 

Justification for 1 Year Ban recommendation:

 

Justification for Lifetime Ban recommendation:

 

Community service details and timeline:

 

Monetary Fine Amount:

Has the player or team filed an appeal?

 

Appeal Filed Timestamp:

 

No appeal filed within the standard 24-hour window.

Esports Integrity Commission Members Review and Approval

Member Name

Member ID

Member Role

Approval of Determination

Member Signature

Signature Date

A
B
C
D
E
F
1
Dr. Samantha Torres
COM-001
Commission Chair
Yes
 
7/15/2025
2
Marcus Webb
COM-012
Technical Expert
Yes
 
7/15/2025
3
 
 
 
 
 
 
4
 
 
 
 
 
 
5
 
 
 
 
 
 
6
 
 
 
 
 
 
7
 
 
 
 
 
 
8
 
 
 
 
 
 
9
 
 
 
 
 
 
10
 
 
 
 
 
 

Final Decision Status

Is a public statement to the community required?

 

Draft Public Statement:

Additional Commission Notes and Dissenting Opinions

Commission Chair Final Signature (approving complete documentation)

Upload Complete Evidence Package (all files zipped and archived)

Choose a file or drop it here
 

To configure an element, select it on the form.

To add a new question or element, click the Question & Element button in the vertical toolbar on the left.