Ink Finance is facing a fresh security incident after its Workspace Treasury Proxy on Polygon was exploited for about $140,000, according to a community alert from Blockaid.
Blockaid said the exploit hit Ink Finance’s Workspace Treasury Proxy “a few minutes” before its alert and estimated the loss at roughly $140,000. The security firm’s post did not immediately provide a full technical breakdown of the attack path, and Ink Finance had not issued a detailed public postmortem at the time of writing.
The affected component is important because treasury proxy contracts can sit close to a project’s operational funds, managed assets, or organization-level financial controls. Ink Finance markets itself as infrastructure for onchain organizations, DAO operations, treasury management, investment workflows, and collaborative financial structures. A Polygon treasury proxy exploit therefore touches the kind of contract layer that protocols use to coordinate assets and execution, not a simple front-end bug.
The early public details remain limited. The confirmed claim is the Blockaid alert: Ink Finance’s Workspace Treasury Proxy on Polygon was exploited for about $140,000. There is no confirmed recovery plan, no public bounty negotiation, and no detailed root-cause disclosure yet. Users and treasury operators tied to Ink Finance should follow the project’s official channels and verify any recovery instructions directly before signing transactions or interacting with replacement contracts.
The incident adds to a growing run of DeFi security alerts involving treasury systems, proxy patterns, and deployment-level mistakes. Proxy contracts are widely used because they let teams upgrade or route logic without redeploying an entire system. That flexibility can also widen the damage if ownership, initialization, upgrade permissions, or migration controls are wrong.
A recent Renegade dark pool exploit showed how quickly a contract-level failure can turn into a live user-funds incident. In that case, the protocol recovered more than 90% of affected assets after an onchain whitehat negotiation. The Ink Finance case is earlier in its response cycle, with the market still waiting for a technical explanation and any user-impact statement.
Polygon remains one of DeFi’s most active execution environments, which keeps contract security under constant pressure. Lower transaction costs and broad tooling make the network attractive for treasury, DAO, and asset-management systems, but the same accessibility can expose older deployments or complex contract stacks when permissions are misconfigured.
The next verified update should come from either Ink Finance or Blockaid. Until then, the clean status is that the Workspace Treasury Proxy on Polygon was exploited for about $140,000, the technical vector has not been fully disclosed publicly, and the affected users or treasury owners still need confirmation on recovery, compensation, contract status, and whether any related Polygon deployments were paused or secured.
The post Ink Finance Treasury Proxy Hit For $140K On Polygon appeared first on Crypto Adventure.
