Skip to content
Connect AISign inSign up free

Bug bounty program

XX

X / xAI

Open on HackerOneAtlas
Platform
HackerOne
Bounties
Pays
Assets in scope
23
Disclosed reports
248
Subdomains
10,596

Most upvoted reports248

All reports
Most upvoted reports of X / xAI
ReportWeaknessDisclosedBountyVotes
Potential pre-auth RCE on Twitter VPNAnalysed#591295Command and Code Injection2019-08-10$20,1601,246
Bypassing Digits origin validation which leads to account takeoverAnalysed#129873Authentication2020-06-24–619
CRLF injectionAnalysed#446271No weakness recorded2019-12-25–439
Read-only application can publish/delete fleetsAnalysed#1032468Access Control2021-01-04–398
Blind XSS on Twitter's internal Big Data panel at █████████████Analysed#1207040Cross-site Scripting2021-07-09–357
Private list members disclosure via GraphQLAnalysed#885539Access Control2020-08-04–346
[Urgent] Invalidating OAuth2 Bearer token makes TweetDeck unavailableAnalysed#210779Denial of Service2019-04-25–323
Bypass Password Authentication for updating email and phone number - Security VulnerabilityAnalysed#770504Authentication2020-02-08–288
Insufficient OAuth callback validation which leads to Periscope account takeoverAnalysed#110293Authentication2019-04-10–277
Insufficient validation on Digits bridgeAnalysed#168116Authentication2020-08-20–263

Subdomains10,596

Root:twitter.com
Scope
Name suggests:Monitoring
First seen
Text fileClear filters37 names
Subdomains of X / xAI
NameScopeFirst seen
splunk.atla.twitter.commonitoringIn scope2026-11-14
splunk-deployer.atla.twitter.commonitoringIn scope2026-11-14
splunk-dma.atla.twitter.commonitoringIn scope2026-11-14
splunk-hec.atla.twitter.commonitoringIn scope2026-11-14
splunk-indexer.atla.twitter.commonitoringIn scope2026-11-14
splunk-master.atla.twitter.commonitoringIn scope2026-11-14
splunk-hec.local.twitter.comdev, monitoringIn scope2026-11-14
monitoring-relay.twitter.commonitoringIn scope2026-11-14
splunk-master.pdx.twitter.commonitoringIn scope2026-11-14
splunk.pdxa.twitter.commonitoringIn scope2026-11-14
splunk-deployer.pdxa.twitter.commonitoringIn scope2026-11-14
splunk-deployer-staging.pdxa.twitter.commonitoring, stagingIn scope2026-11-14
splunk-dma.pdxa.twitter.commonitoringIn scope2026-11-14
splunk-hec.pdxa.twitter.commonitoringIn scope2026-11-14
splunk-hec-staging.pdxa.twitter.commonitoring, stagingIn scope2026-11-14
splunk-indexer.pdxa.twitter.commonitoringIn scope2026-11-14
splunk-master.pdxa.twitter.commonitoringIn scope2026-11-14
splunk-master-staging.pdxa.twitter.commonitoring, stagingIn scope2026-11-14
splunk-staging.pdxa.twitter.commonitoring, stagingIn scope2026-11-14
service-accessibility-monitoring-devel.zone-a.qua2.twitter.comdev, monitoringIn scope2026-11-14
splunk.qus1.twitter.commonitoringIn scope2026-11-14
splunk-deployer.qus1.twitter.commonitoringIn scope2026-11-14
splunk-hec.qus1.twitter.commonitoringIn scope2026-11-14
splunk-master.qus1.twitter.commonitoringIn scope2026-11-14
splunk.smf1.twitter.commonitoringIn scope2026-11-14
splunk-deployer.smf1.twitter.commonitoringIn scope2026-11-14
splunk-deployer-staging.smf1.twitter.commonitoring, stagingIn scope2026-11-14
splunk-hec.smf1.twitter.commonitoringIn scope2026-11-14
splunk-hec-staging.smf1.twitter.commonitoring, stagingIn scope2026-11-14
splunk-indexer.smf1.twitter.commonitoringIn scope2026-11-14
splunk-indexer-staging.smf1.twitter.commonitoring, stagingIn scope2026-11-14
splunk-master.smf1.twitter.commonitoringIn scope2026-11-14
splunk-master-staging.smf1.twitter.commonitoring, stagingIn scope2026-11-14
splunk-staging.smf1.twitter.commonitoring, stagingIn scope2026-11-14
status.twitter.commonitoringIn scope2026-11-14
status.status.twitter.commonitoringIn scope2026-11-14
status1.twitter.commonitoringIn scope2026-11-14

10,296 names are covered by the program's own scope; 0 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.

A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-15.

CyberSIXTSignal over noise
Sign inSign up free

Updated