Earlier today, the attacker behind the recent @binance exploit, apparently in error, sent approximately 8.0M NEWT directly to the NEWT token contract address (0xd0ec028a3d21533fdd200838f39c85b03679285d), along with 17 other tokens: $ANIME, ethereum:0x8290333cef9e6d528dd5618fb97a76f268f3edd4, $ARPA, $BARD, $CELR, ethereum:0x3597bfd533a99c9aa083587b074434e61eb0a258, ethereum:0x0f81001ef0a83ecce5ccebf63eb302c70a39a654, $FTT, $GLM, $HIGH, $HOT, $KNC, $LQTY, $RARE, ethereum:0x259338656198ec7a76c729514d3cb45dfbf768a1, $SIGN and $WOO. These tokens are worth roughly $3.5 million at current prices. To be clear, the NEWT token contract itself was not compromised. We have reviewed the contract carefully, and unfortunately these tokens cannot be recovered. The NEWT token contract was built to be immutable: it has no owner or admin, all admin rights were renounced onchain in 2025, and upgrades are permanently disabled. That design exists to protect holders, so that no one, including the Foundation, can ever move or alter their tokens. These safeguards mean there is no way for anyone to retrieve tokens sent to the contract itself. These tokens are now permanently locked. They are out of the attacker’s control and can never be sold into the market. We have shared our findings with Binance and we will keep helping however we can.

Counterparty risk is the risk associated with who is on the other side of a transaction. Integrations such as @arkham can provide entity identities, wallet roles, and risk tags used by Newton policies when evaluating transactions.

Data oracles provide external data to Newton’s policy engine for evaluation. Integrations such as @redstone_defi can provide asset prices and other financial data used by Newton policies when evaluating transactions.