Troves, a Starknet DeFi strategy platform formerly known as STRKFarm, says its xWBTC/WBTC vault was exploited on October 31, 2026, with a preliminary loss of about 8.6 BTC, roughly $660K at the time. The attacker used a legacy rebalancing contract that had been replaced but kept its permissions. Troves says the loss appears limited to that vault.

Response

Within about 40 minutes Troves revoked the legacy contract and every rebalancer permission on its liquid staking vaults, and paused three vaults: xWBTC/WBTC, xSTRK/STRK and xstrkBTC/strkBTC. In an on-chain message it offered the attacker 1 WBTC to return the rest by November 3, 23:59 UTC. As of the evening of November 3, Troves had not announced any return of funds or published the postmortem and depositor options it promised.

Takeaway

This is an access-control failure, not a bug in new code. Replacing a contract does not remove its roles, approvals or allowlist entries. Teams should make permission revocation a required step of every upgrade, keep an inventory of which addresses hold which roles, test that retired contracts can no longer call sensitive functions, and alert on any call from a contract that should be out of service.

Sources: Troves statements on X and on-chain message (October 31, 2026).