> For the complete documentation index, see [llms.txt](https://reports.immunefi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reports.immunefi.com/plume-or-attackathon/51132-sc-low-tellerwithmultiassetsupportpredicateproxy-cannot-be-paused-unpaused.md).

# 51132 sc low tellerwithmultiassetsupportpredicateproxy cannot be paused unpaused

**Submitted on Jul 31st 2025 at 12:32:34 UTC by @holydevoti0n for** [**Attackathon | Plume Network**](https://immunefi.com/audit-competition/plume-network-attackathon)

* **Report ID:** #51132
* **Report Type:** Smart Contract
* **Report severity:** Low
* **Target:** <https://github.com/immunefi-team/attackathon-plume-network-nucleus-boring-vault/blob/main/src/base/Roles/TellerWithMultiAssetSupportPredicateProxy.sol>
* **Impacts:**
  * Contract fails to deliver promised returns, but doesn't lose value

## Description

## Vulnerability Details

`TellerWithMultiAssetSupportPredicateProxy` inherits from OZ `Pausable` contract but does not expose any function to allow pause/unpause the contract. See OpenZeppelin Pausable implementation:

<https://github.com/OpenZeppelin/openzeppelin-contracts/blob/c3961a45380831135b37e55bc3ed441f678a4f5e/contracts/utils/Pausable.sol#L96-L111>

However, `TellerWithMultiAssetSupportPredicateProxy` uses the `paused` check to prevent deposits in case of emergency:

<https://github.com/immunefi-team/attackathon-plume-network-nucleus-boring-vault/blob/0ee676b5715075c26db6706960fd49ab59b587fc/src/base/Roles/TellerWithMultiAssetSupportPredicateProxy.sol#L78-L80>

```solidity
@> import { Pausable } from "@openzeppelin/contracts/utils/Pausable.sol";
...
@> contract TellerWithMultiAssetSupportPredicateProxy is Pausable {
...
    function deposit(
        ERC20 depositAsset,
        uint256 depositAmount,
        uint256 minimumMint,
        address recipient,
        CrossChainTellerBase teller,
        PredicateMessage calldata predicateMessage
    )
        external
        nonReentrant
        returns (uint256 shares)
    {
@>        if (paused()) {
            revert TellerWithMultiAssetSupportPredicateProxy__Paused();
        }
...
```

## Impact Details

Because the contract does not expose pause/unpause functions, the `paused` check can never be activated by governance or an authorized party. Deposits will continue to be accepted in situations where pausing the contract is desired (e.g., compromise or emergency), preventing mitigation via pausing.

## Recommendation

{% hint style="warning" %}
Add `pause` and `unpause` functions to the contract and restrict them (for example with `onlyOwner` or appropriate access control) so governance or the designated admin can pause deposits in emergencies.
{% endhint %}

## Proof of Concept

**Context**

Governance needs to pause the contract because the vault has been compromised.

{% stepper %}
{% step %}

### Attempt to pause

Governance tries to call the `pause` function, but it does not exist in the `TellerWithMultiAssetSupportPredicateProxy` contract.
{% endstep %}

{% step %}

### Unable to pause

Governance cannot pause the contract because no `pause`/`unpause` functions are exposed.
{% endstep %}

{% step %}

### Continued deposits

Funds continue to flow into the compromised vault (also impacting other contracts that use this one, like `DexAggregatorWrapperWithPredicateProxy`).
{% endstep %}
{% endstepper %}

## References

<https://github.com/OpenZeppelin/openzeppelin-contracts/blob/c3961a45380831135b37e55bc3ed441f678a4f5e/contracts/utils/Pausable.sol#L96-L111>

***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://reports.immunefi.com/plume-or-attackathon/51132-sc-low-tellerwithmultiassetsupportpredicateproxy-cannot-be-paused-unpaused.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.