# Risk Types

Users may opt to be notified when one or more of the following risk type(s) are detected:

<table data-header-hidden data-full-width="true"><thead><tr><th width="337"></th><th></th></tr></thead><tbody><tr><td><strong>Risk Type</strong></td><td><strong>Definition</strong></td></tr><tr><td>Access Role Granted</td><td>An access role grant event was detected in the same transaction as the monitored address.</td></tr><tr><td>Access Role Revoked</td><td>An access role revoke event was detected in the same transaction as the monitored address.</td></tr><tr><td>AI</td><td>A suspicious address that was identified by AI was detected in the same transaction as the monitored address.</td></tr><tr><td>AI Involved</td><td>One of the addresses in this transaction was reported to be malicious by AI.</td></tr><tr><td>Contract Admin Changed</td><td>An admin change event was detected in the same transaction as the monitored address.</td></tr><tr><td>Contract Deployment</td><td>The monitored address was part of a suspicious contract deployment.</td></tr><tr><td>Contract Involved</td><td>This transaction involves a third-party smart contract and its deployer that could possibly be malicious.</td></tr><tr><td>Contract Ownership Changed</td><td>An ownership change event was detected in the same transaction as the monitored address.</td></tr><tr><td>Contract Paused</td><td>A pause event was detected in the same transaction as the monitored address.</td></tr><tr><td>Contract Proxy Admin Changed</td><td>A proxy contract admin change was detected in the same transaction as the monitored address.</td></tr><tr><td>Contract Unpaused</td><td>An unpause event was detected in the same transaction as the monitored address.</td></tr><tr><td>Contract Upgraded</td><td>A contract upgrade event was detected in the same transaction as the monitored address.</td></tr><tr><td>Failed TX</td><td>A failed transaction was detected in the same transaction as the monitored address.</td></tr><tr><td>Flashloan</td><td>A flash loan was detected in the same transaction as the monitored address.</td></tr><tr><td>Known Hacker</td><td>A known hacker address was spotted in the same transaction as the monitored address.</td></tr><tr><td>Mempool TX</td><td>This transaction was spotted in the mempool before it was mined.</td></tr><tr><td>Mixer User</td><td>An address that interacted with Tornado Cash has interacted with the monitored address.</td></tr><tr><td>OFAC Compliance</td><td>An address from the OFAC compliance list has interacted with a monitored address.</td></tr><tr><td>Reentrancy</td><td>A function was called one or more times before the first function call was completed.</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.lossless.io/aegis/triggers/potential-risks/risk-types.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.