Lark · Vulnerability Disclosure

Lark Technologies Vulnerability Disclosure

Vulnerability disclosure

Lark publishes a vulnerability disclosure policy for reporting security issues. A dedicated security contact is published.

CompanyHealthHealthcareDigital HealthChronic Disease ManagementDiabetesHypertensionWeight ManagementArtificial IntelligenceHealth CoachingRemote Patient MonitoringTelehealth
Program:

Disclosure Policy

Policy
https://www.lark.com/responsible-disclosure-policy

Security Contact

Contact
security@lark.com
Contact
https://support.lark.com/hc/en-us/requests/new?ticket_form_id=4584881616148

Source

Vulnerability Disclosure

lark-technologies-vulnerability-disclosure.yml Raw ↑ 
generated: '2026-08-04'
method: searched
probe: true
source: https://www.lark.com/responsible-disclosure-policy
policy:
- https://www.lark.com/responsible-disclosure-policy
contact:
- security@lark.com
- https://support.lark.com/hc/en-us/requests/new?ticket_form_id=4584881616148
bug_bounty:
  program: OpenBugBounty
  url: https://www.openbugbounty.org/bugbounty/larkhealth/
  reward_minimum: USD 100
  reward_form: prepaid Visa gift card
  first_reporter_only: true
  geographic_restriction: >-
    Rewards may not be payable to researchers outside the United States.
policy_details:
  last_updated: '2024-11-18'
  safe_harbor: true
  safe_harbor_text: >-
    "If you have adhered to this Policy, we will not take any legal action against
    you in regard to the report."
  proof_of_concept_required: true
  in_scope:
  - target: lark.com
    note: access control and critical web issues only
  - target: Lark Health Android app
  - target: Lark Health iOS app
  - target: careers.lark.com
    note: write-access vulnerabilities
  - target: support.lark.com
    note: Zendesk-related issues
  out_of_scope:
  - compromised account access
  - policy/configuration disagreements
  - missing security headers
  - open source library vulnerabilities
  - third-party vendor vulnerabilities
  - DoS / DDoS
  - social engineering
  - automated scanner output
  - brute force attempts
security_txt:
  published: false
  note: >-
    No /.well-known/security.txt on any lark.com host (RFC 9116 not adopted), even
    though the disclosure contact security@lark.com is already published on the
    policy page and in the lark.com CAA iodef record. Publishing security.txt would
    be a one-file fix.
evidence:
- source: https://www.lark.com/responsible-disclosure-policy
  kind: disclosure-policy
  http_status: 200
- source: https://www.lark.com/security
  kind: security-page-link
  http_status: 200
- source: 'CAA record lark.com: 0 iodef "mailto:security@lark.com"'
  kind: dns
x-evidence:
  fetched: '2026-08-04'

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/lark-technologies-vulnerability-disclosure"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.