New fund tracing dated November 17 shows where assets moved after a Safe wallet lost approximately $6.44 million on November 16. The update puts the focus on delegated wallet permissions and the limits of identifying stolen funds once they move between services.
In its updated onchain investigation, Bitquery reports that three wallets still held 1,833 ETH, worth about $3.3 million at its snapshot price, at 06:32 UTC on November 17. It also identifies $1.89 million sent through a service associated with Monero swaps.
Safe wallet theft tracing updates the fund picture
The researchers value the original outflow at $6.44 million and describe a transaction executed through a Roles module. They say a wallet with a delegated role signed the transaction, rather than a Safe owner. The November 17 development is the new tracing snapshot, not a new theft that day.
Bitquery says the $1.89 million moved in 12 orders, revising its earlier, lower estimate. Its discussion of a possible Monero payout is an interpretation of service activity. It does not establish a directly visible trail through Monero or identify the person controlling the recipient wallets.
Bitquery did not fully decode the role’s permissions. Some service names use its own labels, limiting conclusions about responsibility.
Delegated modules change how multisignature wallets authorize transactions
Safe wallets commonly use multiple owners and an approval threshold. In a basic arrangement, that can mean requiring several owners to approve a transaction. But additional modules can introduce a separate, previously authorized route for actions.
Safe’s official module documentation explains that modules support automated actions and custom transaction logic alongside the core multisignature mechanism. Owners can authorize a module, after which that module checks requests against its own rules before asking the Safe to execute them.
The documentation gives examples such as recurring payments, allowances and delegated spending. It also warns that modules can execute arbitrary transactions and that a malicious module can take over a Safe. Those are general design characteristics, not an independent diagnosis of this incident.
A transaction without fresh owner signatures therefore does not, by itself, prove that the wallet’s core signature checks failed. The relevant questions include which module was enabled, who could invoke it and what spending or contract permissions that route allowed.
For a treasury team, reviewing only the owner list can miss delegated access. A complete permissions review needs to account for modules, role holders and token approvals as well as the people authorized to sign ordinary transactions.
BlockBriefing’s crypto custody guide discusses the distinction between holding assets and controlling the authority to move them. In a configurable smart-contract wallet, that authority can be spread across several mechanisms.
The tracing figures are a time-limited snapshot. A balance observed at 06:32 UTC can change minutes later, and a dollar valuation changes with the asset price. Neither should be presented as a live balance or a final recovery amount.
Transaction receipt separates token approvals from module authority
A November 17 review of the Ethereum transaction receipt confirms transfers of 4,387,188.426175 USDC and 1,717,918.961706 syrupUSDC from the Safe to one destination. The Safe also recorded an ExecutionFromModuleSuccess event. The exact token quantities are separate from the estimated dollar loss.
Both tokens emitted unlimited approval events during that same transaction, before their outgoing transfers. This does not establish whether earlier allowances existed. It also does not explain which upstream permission allowed the module execution. Token-spending approval and authority to operate a wallet are different controls.
The receipt establishes the execution route and event sequence. A full diagnosis still requires the historical role policy, module implementation and evidence about control of the submitting address. The records reviewed do not establish that an old approval, a stolen key or a code flaw caused the loss.
The available research supports a fund-flow update and a closer look at delegated permissions. It does not establish a platform-wide Safe failure, a confirmed wallet owner or the identity of the thief. Those conclusions require evidence beyond the transfers and documentation reviewed.
