- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 6
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- Partial safe harbor
- Some legal protection; read the terms.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
We do not usually grant monetary rewards for reported vulnerabilities, although exceptions for particularly critical vulnerabilities may be made entirely at Skribble’s discretion.
- Safe harbor
-
Partial
Security research is considered as authorised if you: Conduct your activities in good faith , with the intent of reporting them to us.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
6 assets you may test.
Domains 2
- api.skribble.com
- my.skribble.com
Wildcard domains 2
- *.skribble.cloud
- *.skribble.com
APIs 1
- api.scribital.com (staging)
Web 1
- my.scribital.com (staging)
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Skribble's policy. "We" in these lines means the program, not this site.
While testing
-
Conduct your activities in good faith , with the intent of reporting them to us.
-
Notify us as soon as possible after discovering a security issue.
-
Make reasonable effort to avoid user privacy violations .
-
Immediately cease your activities upon inadvertently accessing sensitive data , notify us of your findings and immediately delete the information from your systems.
-
Only exploit the identified issues to the necessary extent to confirm its presence and produce a proof of concept to demonstrate the attack.
-
Provide us with a reasonable amount of time to investigate, validate and mitigate the issue before publicly disclosing any information about it.
-
Exploit security issues for any reason rather than testing purposes .
-
Intentionally access other user’s account or data without their explicit consent.
-
Intentionally conduct disruptive attacks that could affect systems availability or lead to the destruction of data.
-
Attempt to demand payment or engage in extortion before disclosing security findings to us.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.