Allium Confirms Security Breach, Revokes API Keys as Core Services Return
- Allium confirmed a security breach on October 25, leading to API key revocations and service disruptions.
- Customers must generate new API keys and set new passwords, with multifactor authentication recommended.
- Allium is investigating the breach with a cybersecurity firm and plans to publish findings once complete.
Blockchain data provider Allium has confirmed unauthorized access to some of its systems on October 25, prompting API key revocations and several days of service disruptions. Its main application and Explorer APIs are back online, but the company has not disclosed which systems were compromised or whether customer information was exposed.
In an October 28 security update, CEO and co-founder Ethan Chan said Allium immediately restricted unauthorized access and notified affected customers directly. The company has also hired an independent cybersecurity firm to investigate the breach and is strengthening its authentication and monitoring controls.
The incident disrupted Allium’s blockchain analytics infrastructure, which supplies on-chain data to enterprises and financial institutions, including Visa and Coinbase.
API Keys Revoked as Recovery Continues
Allium’s Explorer first became unavailable on October 25. The company subsequently took its wider application offline on October 26 as a precaution before restoring its Explorer and associated APIs on October 28.
According to its service updates, existing API keys are being revoked. Customers must generate replacement keys through the application unless their Allium representative is providing new credentials directly.
Users are also being asked to set new passwords, with multifactor authentication recommended.
However, several restrictions remain in place. Allium has temporarily disabled both new data uploads and access to previously uploaded datasets, preventing queries that depend on those tables. Allium Assistant and its Model Context Protocol (MCP) service also remain unavailable.
Blockchain Data Feeds Still Require Repairs
The breach response also interrupted Allium’s data delivery infrastructure. Beginning October 26, datashare tables stopped receiving updates, potentially leaving customers with outdated blockchain records or query errors.
By October 28, data delivery had resumed across Snowflake, Databricks and Google BigQuery.
Allium subsequently confirmed that raw and enriched tables covering major networks, including Ethereum, Bitcoin, Solana and Base, had passed completeness and freshness checks on Snowflake and Databricks. Other datasets still required backfilling, including records on BigQuery, while Hyperliquid recovery work remained incomplete.
The remaining gaps mean customers may need to verify historical data completeness even where normal data delivery has resumed.
Allium has not identified the attacker, explained how the intrusion occurred or confirmed whether information was stolen. Chan said the company intends to publish its investigation findings and corrective measures once the independent review is complete, but no release date has been announced.
