# Tutorial 41: Multiple Token Addresses in Proxied Tokens

{% hint style="info" %}
[**Book an audit with Zokyo**](https://www.zokyo.io/)
{% endhint %}

In decentralized finance (DeFi) systems, tokens are often deployed using proxy patterns to enable upgrades without changing the token’s address. However, a common vulnerability arises when proxied tokens have **multiple addresses**. Contracts interacting with these tokens, particularly when handling transfers or safeguarding funds, may incorrectly assume that each token is associated with a single address. This can lead to critical security flaws.

One such vulnerability occurs in the context of **rescue functions**, which are designed to recover tokens mistakenly sent to the contract. If the rescue function assumes a single address per token, proxied tokens with multiple addresses could be incorrectly rescued or drained. This creates an attack vector where the contract owner, under the guise of rescuing tokens, could potentially steal all funds in the pool.

In this section, we will explore how vulnerabilities related to multiple token addresses can arise in proxied tokens and examine the security risks they pose in DeFi protocols.


---

# 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://zokyo-auditing-tutorials.gitbook.io/zokyo-tutorials/tutorial-41-multiple-token-addresses-in-proxied-tokens.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.