Worked example · 2024-08

Nexera (formerly AllianceBlock) NXRA proxy-admin compromise — Ethereum — 2024-08-06

Loss: approximately $1.5M extracted on 2024-08-06 from Nexera (formerly AllianceBlock) via a malicious upgrade of the NXRA token contract executed under a compromised proxy-admin key, followed by an attacker-controlled mint and immediate dump of NXRA into liquidity. Nexera is the rebranded successor of AllianceBlock, a tokenisation / RWA-infrastructure protocol on Ethereum; NXRA is its native ERC-20 governance / utility token administered through an upgradeable-proxy pattern.
Recovery: none of material consequence on the on-chain layer for the dumped value. The protocol team detected the malicious upgrade rapidly, paused trading where possible, coordinated with major centralised exchanges to halt NXRA deposits and trading, and worked with on-chain analytics partners on attempts to track the proceeds. The compromised proxy-admin key was rotated post-incident.
OAK Techniques observed: OAK-T11.002 (Wallet-Software Distribution Compromise) — primary, in the operator-key-compromise sub-class that admits malicious smart-contract upgrades. The proxy-admin key controlling NXRA's upgradeable-proxy pattern was compromised via off-chain means (the public record converges on a credential / personal-device compromise affecting the operator's key-handling environment); OAK-T9.004 (Access-Control Misconfiguration) is the contract-layer framing that classifies the proxy-admin upgrade authority as a single-point-of-failure access-control surface whose compromise admits arbitrary contract logic replacement. The cross-cutting structural lesson is the same as the historical Audius (2022) and Akropolis (2020) governance / proxy-admin cases: when the proxy-admin role can replace the implementation contract, the proxy-admin key is operationally a custody-grade trust surface and must be governed as such.
Attribution: pseudonymous. No public named-individual attribution. Pre-event funding routed through standard mixing infrastructure; post-event laundering routed through DEX hops and mixers. There is no public OAK-G01 / state-actor attribution; OAK-G01 has been publicly active on the operator-key-compromise sub-vector across 2024 (DMM Bitcoin, WazirX, Radiant Capital — all confirmed) but no public forensic claim has placed Nexera in that cluster.
Key teaching point: the upgradeable-proxy admin key is a custody-grade trust surface and must be governed as such, paired with the mint-and-dump extraction shape as the canonical realisation pattern when the compromised authority controls a token's implementation contract. Nexera is the canonical 2024 worked example for the proxy-admin-key-compromise → malicious-upgrade → mint-and-dump pattern, structurally close to Audius 2022 (/examples/2022-07-audius.md — governance-controlled upgrade authority) and Akropolis 2020 (/examples/2020-11-akropolis.md — upgradeable-proxy implementation-replacement vector at function level), but in the specific 2024 sub-pattern where the upgrade authority is a single-key EOA / multisig-of-low-threshold rather than a governance contract. The defender lesson is that proxy-admin authority migration to a multi-signature / time-locked / governance-gated configuration is a discoverable mitigation that has been documented in the audit-firm literature for years; Nexera 2024 is the case that demonstrates the gap between the documented practice and the operational reality.

Summary

Nexera (formerly AllianceBlock) is a tokenisation / real-world-asset infrastructure protocol on Ethereum. The NXRA token is the protocol's native ERC-20 governance / utility token, deployed under an upgradeable-proxy pattern (Transparent Upgradeable Proxy / UUPS-style) where a proxy-admin key controls the authority to replace the underlying implementation contract.

On 2024-08-06 the proxy-admin key was used by an unauthorised party to push a malicious implementation upgrade to the NXRA proxy. The replacement implementation included an attacker-controllable mint path. Immediately after the upgrade, the attacker minted a large quantity of NXRA tokens to attacker-controlled addresses and dumped the minted tokens through Ethereum DEX liquidity venues. Approximately $1.5M of value was extracted from NXRA's standing liquidity before the protocol team detected the attack, paused, and coordinated with centralised exchanges to halt NXRA trading and deposits.

The proximate cause — per the protocol's own post-incident statement and corroborating industry write-ups — is a compromise of the proxy-admin key controlling NXRA's implementation-upgrade authority. The protocol's public statements indicate the compromise occurred at the operator-side key-handling environment (i.e., off-chain on the operator's personnel / device perimeter); the on-chain manifestation was the malicious upgrade transaction signed by the legitimate proxy-admin key.

For OAK's purposes the entry vector is off-chain (the operator-key compromise) and the on-chain manifestation is a textbook proxy-admin-authorised upgrade plus mint-and-dump extraction. The case is the canonical 2024 worked example for the proxy-admin-key-compromise → malicious-upgrade → mint-and-dump pattern, distinguished from the 2024 OAK-G01-attributed supply-chain cohort (DMM Bitcoin, WazirX, Radiant Capital, Bybit) by its smaller scale, its targeting of a token-implementation-replacement surface rather than a custody / signing surface, and its lack of confirmed state-actor attribution.

Timeline (UTC)

When	Event	OAK ref
Pre-event	Nexera deploys NXRA token under upgradeable-proxy pattern; proxy-admin authority controlled by an operator-side key configuration	(T9.004 / T11.002 surface — proxy-admin authority latent)
Pre-event	Off-chain compromise of operator-side proxy-admin key-handling environment; attacker obtains capability to sign as proxy-admin	(off-chain entry vector — out of OAK on-chain scope)
2024-08-06 (attack tx window)	Attacker submits implementation-upgrade transaction signed by the legitimate proxy-admin key; NXRA proxy now points to malicious implementation that admits attacker-controlled minting	T11.002 + T9.004 setup (malicious upgrade)
2024-08-06 (attack tx window)	Attacker mints large quantity of NXRA to attacker-controlled addresses; dumps minted NXRA across Ethereum DEX liquidity venues; extracts ~$1.5M of value	Mint-and-dump extraction
2024-08-06 (within hour)	Nexera operations team detects malicious upgrade and on-chain mint; pauses where possible	(operator response)
2024-08-06 (subsequent)	Nexera coordinates with major centralised exchanges to halt NXRA deposits and trading; engages on-chain analytics partners	(operator response)
2024-08-06 onward	Nexera publishes incident statement; rotates proxy-admin key configuration	(transparency / remediation)
Days following	Attacker laundering routes proceeds through DEX hops and mixers	T7.001 (off this example's framing)
Continuing	NXRA implementation hardened; proxy-admin authority migrated to multi-signature / time-locked configuration per the protocol's post-incident statement	(post-incident hardening)

What defenders observed

The proxy-admin key is a custody-grade trust surface, and Nexera 2024 is the canonical 2024 evidence that the practice has not caught up with the documented standard. Audit-firm literature on upgradeable-proxy patterns has documented for years that the proxy-admin role admits arbitrary contract-logic replacement and must be governed as a custody-grade trust surface (multi-signature with adequate threshold, time-locked, ideally governance-gated for tokens with material standing liquidity). Nexera's operative configuration at the time of the incident was lighter than this standard. The defender lesson is that the gap between documented best practice and operational reality is meaningful, and proxy-admin authority configuration is an audit-checkable parameter that risk teams should treat as first-class.
The mint-and-dump extraction shape is the canonical realisation pattern when the compromised authority controls a token's implementation contract. Once the attacker controls the implementation, the attacker has full latitude over the token's logic, including the supply curve. The fastest extraction path is to add a mint capability to the implementation, mint to attacker-controlled addresses, and dump the minted supply into existing liquidity before the market or operator can react. The pattern is structurally identical at Audius 2022 (/examples/2022-07-audius.md — governance-controlled upgrade authority compromised, mint-and-dump of AUDIO into liquidity) and similar in mechanism at Akropolis 2020 (/examples/2020-11-akropolis.md — upgradeable-proxy implementation replacement at function level with downstream extraction). The recovery rate for this extraction shape is operationally bounded by speed-of-detection and CEX-coordination effectiveness; the on-chain extraction itself is rarely reversible because the dumped tokens have already been swapped through the standing liquidity by the time the protocol team detects.
CEX coordination is a partial-recovery mitigation that has the highest ROI when invoked within the same transaction window as the dump. Nexera coordinated with major centralised exchanges to halt NXRA deposits and trading rapidly after detection. This bounds the attacker's ability to off-ramp via CEX rails but does not unwind the on-chain dump that has already extracted from DEX liquidity. The standard 2024 lesson — same as Audius 2022 — is that CEX coordination is necessary but not sufficient for material recovery; the load-bearing mitigation is preventing the upgrade authority from being compromisable in the first place.
Detection latency was operator-acceptable but recovery was effectively foreclosed by the extraction shape. Nexera detected and responded within the same hour as the attack window. By that time the dumped tokens had already extracted value from DEX liquidity; the on-chain pause primitive on a token contract does not unwind completed swaps. The structural ceiling for this extraction shape is rapid detection plus CEX coordination plus token-implementation hardening — not on-chain recovery of the dumped value.
Pseudonymous attribution is the realistic attribution status; OAK-G01 has been active on the operator-key sub-vector through 2024 but Nexera is not in the publicly-confirmed cluster. OAK-G01 (DPRK-attributed) has been publicly confirmed at DMM Bitcoin (May 2024), WazirX (July 2024), Radiant Capital (October 2024), and Bybit (February 2025), all on the operator-side / vendor-side key-compromise sub-vector. Nexera is not in this publicly-confirmed cluster; the pseudonymous attribution does not preclude OAK-G01 involvement but it is not asserted in the public forensic record and contributors should not over-claim.

What this example tells contributors writing future Technique pages

T11.002 covers the operator-key proxy-admin-compromise sub-class, and Nexera 2024 is the canonical 2024 worked example. The cohort spans Akropolis 2020 (upgradeable-proxy implementation-replacement at function level), Audius 2022 (governance-contract-controlled upgrade authority compromise), and now Nexera 2024 (single-key / low-threshold proxy-admin compromise on a token implementation). The T11.002 / T9.004 technique pages should treat the operator-key proxy-admin-compromise sub-class as a discrete sub-class alongside vendor-side wallet-software-distribution compromise (DMM 2024) and third-party signing-platform compromise (Bybit 2025).
The mint-and-dump extraction shape is a canonical realisation pattern for token-implementation-control compromises. Worked examples for token-contract-control compromises should make the extraction shape explicit in the timeline. The defender mitigation is upstream — making the upgrade authority non-compromisable — because the extraction shape is operationally fast and recovery is structurally bounded by detection latency.
Proxy-admin authority configuration is an audit-checkable parameter that risk teams should treat as first-class. The configuration is on-chain readable (proxy-admin address, multisig threshold if applicable, time-lock presence and duration). Cohort-level surveillance of upgradeable-proxy tokens with single-key or low-threshold proxy-admin configurations is a discoverable defender practice.
CEX coordination is a necessary-but-not-sufficient mitigation; the load-bearing mitigation is upgrade-authority hardening. Worked examples should not let CEX-coordination success anchor expectations away from the upstream mitigation. CEX coordination bounds the attacker's off-ramp but does not unwind the on-chain dump.
Pseudonymous attribution is the realistic attribution status for cases not in publicly-confirmed OAK-Gnn clusters. Contributors should not infer state-actor attribution from operational shape alone; the publicly-confirmed OAK-G01 2024 cluster is well-defined and Nexera is not in it.

Public references

[nexerapostmortem2024] — Nexera protocol-side post-incident statement covering the malicious upgrade, the mint-and-dump extraction, the rapid-response CEX coordination, and the proxy-admin key configuration changes.
[blocksecnexera2024] — BlockSec PhalconHQ forensic transaction-trace analysis of the malicious upgrade transaction and the subsequent mint-and-dump sequence into Ethereum DEX liquidity.
[slowmistnexera2024] — SlowMist incident analysis covering the proxy-admin compromise framing and laundering tracking.
[peckshieldnexera2024] — PeckShield headline figures and on-chain analytics for the Nexera drain.
[rektnexera2024] — Rekt News public-facing summary framing the case as a proxy-admin-key-compromise → malicious-upgrade → mint-and-dump pattern.

Citations

[nexerapostmortem2024] — Operator post-incident statement; primary source for affected-surface identification, response timeline, and post-incident hardening.
[blocksecnexera2024] — Forensic transaction-trace analysis; primary source for the malicious-upgrade and mint-and-dump root-cause walkthrough.
[slowmistnexera2024] — Forensic incident analysis; primary source for the proxy-admin compromise framing.
[peckshieldnexera2024] — Headline figures and on-chain analytics; primary source for cited $1.5M loss figure.
[rektnexera2024] — Public-facing summary; secondary source for the canonical-pattern framing.

Discussion

Nexera 2024 is OAK's canonical 2024 worked example for the proxy-admin-key-compromise → malicious-upgrade → mint-and-dump pattern, paired with Audius 2022 (governance-controlled upgrade authority compromise) and Akropolis 2020 (upgradeable-proxy implementation-replacement at function level) as cohort cases under the broader T11.002 / T9.004 surface. The case is structurally distinct from the OAK-G01 2024 supply-chain cohort (DMM, WazirX, Radiant, Bybit) by scale, by target surface (token-implementation control rather than custody / signing), and by attribution (pseudonymous rather than confirmed state-actor).

The cohort framing for the proxy-admin-key-compromise sub-class is well-established by 2024. Audit-firm literature has documented the structural risk of single-key / low-threshold proxy-admin authority for years; the OpenZeppelin Upgrades plugin, Transparent Upgradeable Proxy and UUPS proxy patterns, and the surrounding audit-checklist tradition all flag the proxy-admin role as a custody-grade trust surface. The Nexera case is the canonical 2024 evidence that the documented practice has not been operationalised across the deployed-protocol cohort with sufficient coverage to prevent the case class from continuing to fire.

The mint-and-dump extraction shape is the second analytically distinctive feature. Once the attacker controls the implementation, the attacker has full latitude over the token's logic, and the fastest extraction path is to add a mint capability and dump the minted supply into existing liquidity. The recovery rate for this extraction shape is operationally bounded by speed-of-detection and CEX-coordination effectiveness; on-chain recovery of the dumped value is rarely achieved because the swaps have already executed against standing DEX liquidity by the time the protocol team detects.

For OAK's broader credibility, including Nexera in v0.1 closes a 2024 gap on the proxy-admin-key-compromise sub-class. The 2024 corpus is heavy on the OAK-G01 supply-chain cohort (DMM, WazirX, Radiant, with Bybit in early 2025) and on the smart-contract-bug cohort (Penpie, Onyx, UwU Lend, Pike Finance), but the operator-key proxy-admin-compromise sub-class — pseudonymous attacker, smaller scale, token-implementation-control target — is also a 2024 reality. Nexera is the canonical 2024 worked example for this sub-class and pairs structurally with the Audius / Akropolis historical precedents to make the cross-cutting OAK lesson — that the upgrade authority is a custody-grade trust surface and must be governed as such — legible at the corpus level.