Incident Update: Third-Party Tooling Issue and Our Response

We are aware of claims circulating online regarding a potential security incident. We promptly initiated a review in line with our security protocols to assess the situation.

What we identified

Our review identified that a limited number of internal repositories were exposed in connection with a third-party security tooling issue involving Trivy on GitHub.

This exposure did not result in unauthorized access to our production systems or live environments.

Scope of impact

The exposure was limited to a subset of internal repositories.

No unauthorized access to production systems or live environments occurred.

What was not affected

• No customer data was accessed or compromised
• No trading accounts or information were impacted
• No production systems were affected

Our platform remains fully operational, with no impact to customers or partners.

Actions taken

Upon identification, we acted immediately to:

• Secure all affected repositories
• Rotate all relevant credentials and access tokens
• Audit systems, access logs, and permissions across environments

These steps were taken to ensure the integrity and security of our systems.

Security posture

Security is embedded into how we build and operate. We maintain continuous monitoring, enforce strict access controls, and conduct regular audits across our infrastructure, supported by established security practices and industry-standard tooling.

‍