Skip to content
Connect AISign inSign up free

Bug bounty program

SL

Slack

Open on HackerOneAtlas
Platform
HackerOne
Bounties
Pays
Assets in scope
19
Disclosed reports
133
Subdomains
137,436

Most upvoted reports133

All reports
Most upvoted reports of Slack
ReportWeaknessDisclosedBountyVotes
Mass account takeovers using HTTP Request Smuggling on https://slackb.com/ to steal session cookiesAnalysed#737140Injection and Smuggling2020-03-12–870
Remote Code Execution in Slack desktop apps + bonusAnalysed#783877Command and Code Injection2020-08-28–509
XSS vulnerable parameter in a location hashAnalysed#146336Cross-site Scripting2019-10-16–455
URL link spoofingAnalysed#481472Input Validation and Logic2020-04-26$250362
TURN server allows TCP and UDP proxying to internal network, localhost and meta-data servicesAnalysed#333419Server-Side Request Forgery2020-03-12$3,500323
AWS bucket leading to iOS test build code and configuration exposureAnalysed#404822Information Disclosure2019-02-23$1,500321
Slack DTLS uses a private key that is in the public domain, which may lead to SRTP stream hijackAnalysed#531032Cryptography2020-03-12$2,000170
XSS in gist integrationAnalysed#11073Cross-site Scripting2019-04-28$500157
Unauthenticated LFI revealing log informationAnalysed#272578Information Disclosure2018-01-26–123
Stealing xoxs-tokens using weak postMessage / call-popup redirect to current team domainAnalysed#207170Misconfiguration and Insecure Design2017-02-28–120

Subdomains137,436

Root
Scope
Name suggests:Monitoring
First seen
Text fileClear filters296 names
Subdomains of Slack
NameScopeFirst seen
elk.quip.commonitoringIn scope2026-11-14
logging.quip.commonitoringIn scope2026-11-14
logs.quip.commonitoringIn scope2026-11-14
metrics.quip.commonitoringIn scope2026-11-14
monitor.quip.commonitoringIn scope2026-11-14
www.monitor.quip.commonitoringIn scope2026-11-14
monitor2.quip.commonitoringIn scope2026-11-14
monitor3.quip.commonitoringIn scope2026-11-14
monitoring.quip.commonitoringIn scope2026-11-14
www.monitoring.quip.commonitoringIn scope2026-11-14
monitoring2.quip.commonitoringIn scope2026-11-14
nagios.quip.commonitoringIn scope2026-11-14
nagios2.quip.commonitoringIn scope2026-11-14
prometheus.quip.commonitoringIn scope2026-11-14
sentry.quip.commonitoringIn scope2026-11-14
splunk.quip.commonitoringIn scope2026-11-14
status.quip.commonitoringIn scope2026-11-14
www.status.quip.commonitoringIn scope2026-11-14
zabbix.quip.commonitoringIn scope2026-11-14
www.zabbix.quip.commonitoringIn scope2026-11-14
zabbix2.quip.commonitoringIn scope2026-11-14
24metrics.slack.commonitoringNot in the scope2026-11-14
amis-prometheus.slack.commonitoringNot in the scope2026-11-14
metrics.api.slack.comapi, monitoringNot in the scope2026-11-14
metrics.app.slack.commonitoringNot in the scope2026-11-14
status.dev.slack.comdev, monitoringNot in the scope2026-11-14
elk.slack.commonitoringNot in the scope2026-11-14
elk-stack-group.slack.commonitoringNot in the scope2026-11-14
grafana.slack.commonitoringNot in the scope2026-11-14
logging.slack.commonitoringNot in the scope2026-11-14
logs.slack.commonitoringNot in the scope2026-11-14
metrics.slack.commonitoringNot in the scope2026-11-14
micrometer-metrics.slack.commonitoringNot in the scope2026-11-14
monitor.slack.commonitoringNot in the scope2026-11-14
www.monitor.slack.commonitoringNot in the scope2026-11-14
monitor1.slack.commonitoringNot in the scope2026-11-14
monitor2.slack.commonitoringNot in the scope2026-11-14
monitor3.slack.commonitoringNot in the scope2026-11-14
monitoring.slack.commonitoringNot in the scope2026-11-14
www.monitoring.slack.commonitoringNot in the scope2026-11-14
monitoring2.slack.commonitoringNot in the scope2026-11-14
nagios.slack.commonitoringNot in the scope2026-11-14
nagios2.slack.commonitoringNot in the scope2026-11-14

20,412 names are covered by the program's own scope; 7 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