> For the complete documentation index, see [llms.txt](https://docs.salusec.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.salusec.io/untitled/web3-penetration-test.md).

# Web3 Penetration test

- [Web3 Penetration Test Overview](https://docs.salusec.io/untitled/web3-penetration-test/web3-penetration-test-overview.md): WEB3 penetration testing refers to the security testing of applications built using blockchain technology. The main goal is to find security vulnerabilities and provide repair suggestions.
- [Risks in GameFi](https://docs.salusec.io/untitled/web3-penetration-test/risks-in-gamefi.md): GameFi applications are considered high-risk areas for WEB3 penetration testing due to their large user base, diverse interaction scenarios, and the complexity of the games themselves.
- [Risks in DeFi](https://docs.salusec.io/untitled/web3-penetration-test/risks-in-defi.md): DeFi projects should not only pay attention to the vulnerabilities related to smart contracts, but the security risks related to non-smart contracts are also fatal to DeFi applications.
- [Risks in Cefi](https://docs.salusec.io/untitled/web3-penetration-test/risks-in-cefi.md): Penetration testing for CeFi platforms involves addressing information leakage, account security, system security, and business scenario security risks.
- [Risks in social media](https://docs.salusec.io/untitled/web3-penetration-test/risks-in-social-media.md): Decentralized blockchain products are prone to phishing attacks. Security issues in common crypto communication software require users to be more cautious.


---

# 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://docs.salusec.io/untitled/web3-penetration-test.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.