Blockchain Data Firm Allium Says Every Chain Passed Checks After Security Incident

Allium confirmed that its blockchain data feeds on Snowflake, BigQuery and Databricks have passed verification checks for every chain, but the cause and scope of the earlier unauthorized access remain undisclosed pending a third‑party investigation.

Blockchain Data Firm Allium Says Every Chain Passed Checks After Security Incident

Introduction

Allium, a leading provider of on‑chain data for institutions such as Visa, KPMG and Coinbase, announced that its data shares on Snowflake, BigQuery and Databricks have successfully cleared historical verification checks for every blockchain it supports. This update comes five days after the company disclosed an unauthorized access incident that disrupted its Explorer app and API services.

What Happened

  • Incident timeline: Allium detected suspicious activity on Oct. 25, publicly disclosed it on Oct. 28, and began restoring services on Oct. 28. The Explorer app was offline for roughly 61 hours, and data delivery to its Snowflake, BigQuery and Databricks datashares paused for just under 24 hours.
  • Current status: As of the latest status‑page update, all datashare tables across every region are back online and have passed verification checks. However, the Explorer UI, Explorer Queries, and some ancillary tools (Allium Assistant, Allium MCP) remain in a partial‑outage state.

What Allium Has Not Yet Explained

The company’s statement, signed by CEO Ethan Chan, omitted several critical details:

  1. Root cause – No information on how the unauthorized access was achieved or who was responsible.
  2. Data exposure – It is unclear whether any customer data, API keys, or proprietary blockchain snapshots were accessed or exfiltrated.
  3. Customer impact – Allium has not disclosed how many clients were affected or whether any services beyond the Explorer were compromised.
  4. Link to datashare outage – The relationship, if any, between the security breach and the temporary halt in data delivery remains unspecified.

Allium has engaged an independent cybersecurity firm to investigate and promises to publish a summary of findings once the review is complete.

Mitigation Steps for Customers

While the investigation proceeds, Allium has taken several precautionary actions:

  • API key rotation – Existing keys were revoked; customers must generate new keys via the app or through direct contact with Allium representatives.
  • Credential hardening – Users are urged to reset passwords and enable multi‑factor authentication (MFA).
  • Feature restrictions – Uploading new data and accessing previously uploaded datasets are temporarily disabled to prevent potentially compromised queries from executing.

Customers should monitor Allium’s status page for updates on the restoration of the Explorer UI, Explorer Queries, and ancillary tools, and be prepared to adjust their integration pipelines accordingly.

Looking Ahead

Allium’s quick restoration of its datashares demonstrates operational resilience, but the lack of transparency around the breach’s cause and scope leaves open questions about long‑term security posture. Stakeholders will be watching for:

  • The forthcoming third‑party investigation report, which should detail the attack vector and any data that may have been accessed.
  • Additional security enhancements, particularly around authentication, monitoring, and access controls.
  • Communication from affected customers (e.g., Visa, KPMG, Coinbase) regarding any internal impact assessments.

Conclusion

Allium has successfully verified that its blockchain data feeds are intact across all supported chains, but the incident underscores the importance of clear, timely disclosure in the crypto‑infrastructure space. Until the investigation’s findings are released, customers should treat the situation as a reminder to enforce strong credential hygiene and stay alert for further updates from Allium.

Source

Read original source

Why we picked this

Primary security incident follow‑up from the data firm itself

← Back to all articles