- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 1
- 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]
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
The policy page does not state reward amounts that we could read. Check it before you test.
Scope
1 asset you may test.
Domains 1
- larksuite.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Lark's policy. "We" in these lines means the program, not this site.
While testing
-
You must be the first reporter to report the issue to us. We will only reward the first reporter.
-
When submitting a vulnerability, please provide us with enough information so that we can reproduce and verify it.
-
Please use your own account for testing purposes. Do not gain access to another user's account or their confidential information.
-
Please do not test for denial of service, spam, social engineering issues.
-
All of the tests must not violate any law, or compromise any data that is not your own.
-
Please contact [email protected] to report security incidents such as customer data leakage or breach of infrastructure
-
Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
-
Submit one vulnerability per-report, unless you need to chain vulnerabilities to provide impact.
-
When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
-
Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
Not accepted
-
Reports from automated tools or scans
-
Spam vulnerability, mail spoofing, mail bomb, etc.
-
Self-XSS
-
Use of known-vulnerable library or component
-
Clickjacking on pages with no sensitive actions
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
-
Attacks requiring MITM or physical access to a user's device.
-
Previously known vulnerable libraries without a working Proof of Concept.
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
-
Missing best practices in SSL/TLS configuration.
-
Any activity that could lead to the disruption of our service (DoS).
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Rate limiting or bruteforce issues on non-authentication endpoints
-
Missing best practices in Content Security Policy.
-
Missing HttpOnly or Secure flags on cookies
-
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
-
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
-
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
-
Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
-
Tabnabbing
-
Open redirect - unless an additional security impact can be demonstrated
-
Issues that require unlikely user interaction
-
Vulnerabilities that are already known (e.g. discovered by an internal team)
-
Best practice" reports are not eligible for bounties but are appreciated.
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.