> For the complete documentation index, see [llms.txt](https://whitepaper.virtuals.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.virtuals.io/info-hub/security/virtuals-protocol-security-policy-and-vulnerability-disclosure.md).

# Virtuals Protocol Security Policy and Vulnerability Disclosure

### Responsible disclosure and bug bounty program

Virtuals Protocol is working with [Immunefi](https://immunefi.com/) on a comprehensive bug bounty program.

### Report a security vulnerability

Security is a priority at [Virtuals Protocol](https://app.virtuals.io/). We have paid over $30,000 in bounties as of August 5, 2025. We thank security researchers who report vulnerabilities responsibly.

If you identify a security vulnerability, email <security@virtuals.io> with:

* A detailed description of the vulnerability
* Steps to reproduce
* Potential impact of the vulnerability
* Any possible methods to mitigate that you have identified

### Vulnerability report response timeline

* An initial response in **24 hours** to acknowledge that we have received your report
* Updates are provided every 3 business days about progress
* Resolution no later than 15 days for critical issues
* We will coordinate public disclosure timing with you

Do not publish on blogs, X, or elsewhere until we fix the issue. We will coordinate public disclosure with you.

### Vulnerability disclosure scope

Everything Virtuals Protocol touches is in scope. This includes:

* Smart contracts
* SDKs
* Production-ready repository code, including [Virtuals Protocol](https://github.com/Virtual-Protocol) and [G.A.M.E](https://github.com/game-by-virtuals)

### Security researcher recognition and bounty rewards

We recognize security researchers who improve critical infrastructure security. Contributors are:

* Credited in security acknowledgements
* Paid a bounty for finding security issues

#### How bug bounty rewards are determined

* **Quality of description:** Provide a well-written submission.
* **Reproducibility:** Include a proof of concept (POC). Code, scripts, and details improve reproducibility and rewards.
* **Quality of fix:** Include a fix to qualify for a higher reward.

We use the [CVSS Score](https://nvd.nist.gov/vuln-metrics/cvss) to determine fair payments.

### Security contact

Report security issues to <security@virtuals.io>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://whitepaper.virtuals.io/info-hub/security/virtuals-protocol-security-policy-and-vulnerability-disclosure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
