Can one person move the money in USDtb (Ethena Labs) on Ethereum? The authority score is 2 / 100 (critical): one key or a tiny group.
In short. A single bare EOA - a real, actively-used key, not vanity-mined - holds both DEFAULT_ADMIN_ROLE and the ProxyAdmin owner() on a $483M stablecoin. No Safe, no Timelock, no DAO anywhere.
Exposure, not intent. The score counts what the keys could do, not what their holders will do, and says nothing about the odds of a loss. Re-read it yourself with a public RPC and curl: how.
Try a fix: drag the sliders Open the live dashboard re-read from the chain every 6 hours; this page is the snapshot of the build
| admin key | 5 |
|---|---|
| multisig | 0 |
| timelock | 0 |
| price feed | 100 |
| shared control | 100 |
Composite = 40% admin key + 30% multisig + 30% timelock, rounded. Price feed and shared control are read and shown, not folded in.
To move the money: 1 key, 0 h to react, about $476M behind one key.
A single bare EOA - a real, actively-used key, not vanity-mined - holds both DEFAULT_ADMIN_ROLE and the ProxyAdmin owner() on a $483M stablecoin. No Safe, no Timelock, no DAO anywhere.
critical: bare EOA on $483M
The same EOA also independently holds admin on two other proxies (fUSD, aBTC) with negligible real usage, so those aren’t scored as their own targets - but the blast radius is real. Genuinely inconsistent within Ethena’s own infrastructure: USDtb’s own PSM (next card) migrated from a Safe to a real 24h Timelock on 2026-07-13; this token’s upgrade authority never got the same treatment.
Exit window: none: a change applies at once, the time a user has to leave after a harmful change is queued.
If a market used the example policy today (src/ExampleConsumer.sol: revert when stale, 0 under 60, 50% to 80% above): collateral factor 0 (score 2 is under MIN_SAFE_SCORE 60). Cheapest path to weak (20): admin key from 5 to 49, that is a stronger admin setup (admin power spread beyond one key, or checked by others), every other axis unchanged. This is the smallest step into the next band, not a fix for the weakness: the first requirement not met is Admin power is not a bare key (one key, or a tiny group, can change it).
[](https://realspap.github.io/oracle/p/ethereum-l1-0xc139190f447e929f090edeb554d95abb8b18ac1c.html)
A live badge: the score is read from the published watch files every time the page that shows it loads. Change nothing but your own repository.
Money behind it: $476M (DefiLlama), of which $466M sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0xc139190f447e929f090edeb554d95abb8b18ac1c on the explorer ↗. Score pushed on-chain on 2026-10-13; stale on the oracle when older than 9 days (the watch re-reads it anyway). Read the score yourself: getScore(0xc139190f447e929f090edeb554d95abb8b18ac1c) on the Ethereum oracle, listed in the repository.
Read at block 11922317, methodology 0x46a1a85b619e7db0…. The score reads the authority path (keys, multisigs, timelocks, roles, price feeds); it does not audit the code for bugs, and it measures exposure, not the chance of being hit (see the backtest in the repository). Dispute this score with evidence, or read this page as JSON.
Read live: admin: a plain key, 13 transactions sent; delay: none.
Independent read of the admin: a plain key (bare EOA) 0xd938…395…3956 via EIP-1967 admin -> ProxyAdmin owner(), consistent with the published admin-key score. Unchanged since 2026-10-10. This key has sent 13 transactions. The attacker's question: 1 key moves this contract, no delay to react, $476M behind each key (the protocol's TVL, not this contract's balance). Implementation behind the proxy: 0x9d6d77a21702b9afcf924983fbfb84aaaae79589 (EIP-1967 implementation slot). Its source is verified on Sourcify (AnchorageTokenUSDtb, match, 0.8.30+commit.73712a01). (scripts/second_opinion.py: a reader that shares nothing with the scorer, re-run every 6 hours)
Score unchanged since its publication on 2026-10-13; every later move will be a line of the hash-chained log. Methodology changed on 2026-10-13: points before that date come from another method and are not comparable.
# the admin slot of the proxy (EIP-1967): the word is the admin address
curl -s -X POST https://ethereum-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getStorageAt","params":["0xc139190f447e929f090edeb554d95abb8b18ac1c","0xb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d6103","latest"]}'
# owner() on the address the slot returned (a ProxyAdmin): the holder
curl -s -X POST https://ethereum-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"<address from the slot>","data":"0x8da5cb5b"},"latest"]}'
# eth_getCode on the holder: 0x means a plain key
curl -s -X POST https://ethereum-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getCode","params":["<holder>","latest"]}'
# the implementation slot of the proxy (EIP-1967): the code behind it, an upgrade changes this word
curl -s -X POST https://ethereum-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getStorageAt","params":["0xc139190f447e929f090edeb554d95abb8b18ac1c","0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc","latest"]}'
# eth_getTransactionCount on the holder: how many transactions this key has sent (13 at the read)
curl -s -X POST https://ethereum-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getTransactionCount","params":["<holder>","latest"]}'Each answer is a 32-byte word (an address sits in its last 20 bytes); the admin path is the one scripts/second_opinion.py reports for this contract. read between blocks 26199869 and 26199870 of the chain; this RPC cannot replay the block of the read (it ignores the block tag, or no longer serves old state): the answers are the current ones
Follow this contract: Atom feed of its score moves, alerts and queued operations (nothing else).
curl -s -X POST https://ethereum-sepolia-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xB6F8474ccC71AF477c31c2DF663B3942ddfbf906","data":"0xd47875d0000000000000000000000000c139190f447e929f090edeb554d95abb8b18ac1c"},"0xb5eb8d"]}'The 6th 32-byte word of the answer is the composite score (2 = 0x2); the 7th is the push timestamp. Same call with "latest" instead of the block gives the current value.