> ## Documentation Index
> Fetch the complete documentation index at: https://docs.raydium.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Security & Risk

> Audit history, admin controls, known risk surface, attack vectors, and responsible disclosure.

## Who this chapter is for

Auditors, security researchers, risk teams at integrators, and institutional users who need to evaluate Raydium before deploying capital or code against it.

## Chapter contents

> [card] [Audits](https://docs.raydium.io/security/audits.md)
>
> Full list of audits per program, with audit firm, scope, report links, and follow-up fix status.

> [card] [Admin keys and multisig](https://docs.raydium.io/security/admin-and-multisig.md)
>
> Which authorities exist per program, what they can change, how they are controlled (multisig, timelock), and how to verify on-chain.

> [card] [Oracle and token risks](https://docs.raydium.io/security/oracle-and-token-risks.md)
>
> Oracle usage and failure modes, Token-2022 extension risks (freeze authority, transfer hook, permanent delegate), and how Raydium mitigates them.

> [card] [Attack vectors](https://docs.raydium.io/security/attack-vectors.md)
>
> Historical and hypothetical vectors: sandwich/MEV, price manipulation, donation attacks, Token-2022 hook abuse, composability risks.

> [card] [Disclosure](https://docs.raydium.io/security/disclosure.md)
>
> Responsible-disclosure policy, bug bounty scope, contact paths, and what *not* to disclose publicly.

## Writing brief

* Cite specific on-chain accounts/program IDs for every claim about authority or mitigation.
* Do not publish private admin procedures or operational runbooks here.
* Keep historical-incident writeups factual and link to post-mortems where they exist.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.