Chainstack Hit by AI-Driven ARTEX Breach Exposing Customer Data and Password Hashes
Blockchain infrastructure provider Chainstack has confirmed that an outside attacker accessed parts of its systems between October 26 and October 31, 2026. The attacker reached a customer account database and systems that hold node credentials. Chainstack says the intrusion was part of a wider AI-powered attack campaign and that its customer-facing services kept running normally throughout.
Chainstack published its incident report on November 3 and added technical findings, indicators of compromise (IoCs) and an expanded timeline on November 10. The page was last updated on November 11. The company also disclosed the incident in a public statement on X on November 3. It is emailing all customers and asking them to change passwords, rotate node credentials, and regenerate platform API keys.
Chainstack will enforce stricter credential policies, likely mandating MFA and eliminating default passwords on all test servers.
Customers must rotate node credentials and API keys, prompting industry-wide reviews of shared infrastructure security practices.
The ARTEX AI-driven attack model may inspire similar campaigns, pushing regulators to consider new standards for blockchain service providers.
What Chainstack Does
Chainstack runs blockchain nodes for developers and businesses. A node is a computer that keeps a copy of a blockchain and passes transactions to the network. Wallets, trading tools, and decentralized applications (DApps) often connect to nodes run by providers like Chainstack instead of running their own. They connect using node credentials, the access details that tie each endpoint to a customer account.
That position between applications and blockchains is why a breach at an infrastructure provider matters beyond the provider itself.
How the Attacker Got In
The report says the entry point was a Grafana instance deployed for testing. Grafana is an open-source tool for monitoring dashboards. This instance was reachable from the internet and still used its default administrator credentials. It had no extra protection such as single sign-on (SSO) or basic authentication. It had been running in a development Kubernetes cluster since July 2026. Kubernetes is a system for running and managing software containers.
The attacker used Grafana’s data source proxy, a feature that forwards requests to connected services, to reach internal systems. One of these was a Model Context Protocol (MCP) tool server that required no authentication and ran with cluster-admin rights. MCP is an open standard that lets AI applications call external tools and data sources.
From the development environment, the attacker obtained machine credentials that also worked in production. Chainstack says it found no evidence that a software vulnerability was exploited. Instead, the intrusion combined five weaknesses:
- Default credentials
- Exposed administrative functions
- Missing authentication
- Over-broad permissions
- Long-lived credentials
Timeline of the Attack
The report gives all times in Coordinated Universal Time (UTC):
- July 2026: A test Grafana instance was deployed to a development Kubernetes cluster with default admin credentials and no extra authentication layer.
- October 26, 19:26: First observed use of the Grafana data source proxy to reach internal services. The attacker later connected to the unauthenticated MCP tool server.
- October 26 to 27: The attacker injected JavaScript loaders into development and staging web applications. The loaders referenced a second-stage script hosted on silverbullet[.]icu.
- October 29: The attacker used compromised development cloud credentials and hijacked an automation workflow to obtain more machine identities. Production Kubernetes secrets were listed and read.
- October 30: Persistence mechanisms were installed on development hosts. DNS and edge API tokens were used for reconnaissance.
- October 31, about 01:40 to 08:31: Bulk reads from the production cloud secrets manager. New keys and identities were created. A compromised virtual private network (VPN) key was used to connect to the database network. This disrupted database replication and triggered detection.
- October 31: Database queries ran from attacker-controlled pods, including queries against PostgreSQL’s pg_shadow view, which stores role password hashes. Chainstack cut the access paths the same day.
- November 2: Last observed use of a previously copied credential. Chainstack finalized and closed its investigation.
What Data Was Exposed
The attacker accessed a database of customer account information. Chainstack says the data that may have been exposed includes:
- Organization names
- Account holder names
- Email addresses of organization members on Chainstack
- Password hashes
The attacker also had access to systems holding node credentials. Chainstack says it has no evidence that these credentials were read but is treating them as exposed and requiring rotation. It says there is no evidence that customer nodes, the console or the API were modified. Full payment card details are not stored by Chainstack, so they were not exposed.
Chainstack has not disclosed how many customer accounts or organizations were affected.
What Is ARTEX?
Chainstack says it assesses with high confidence that the attacker used ARTEX. ARTEX is an open-source penetration testing framework that coordinates large language model (LLM) agents to automate intrusion steps. Penetration testing means authorized, simulated attacks run to find security weaknesses. In this incident, Chainstack found consistent “artx” and “artex” naming markers in artifacts across the attacker’s activity.
ARTEX was built for authorized security testing, but it has already been used in real attacks. On October 7, CrowdStrike reported that an unidentified threat actor used ARTEX, which it describes as a Chinese-developed agentic penetration testing tool, against South Korean financial organizations. That campaign ran from late September to early October 2026 and resulted in data being stolen. Chainstack says researchers have also linked the framework to activity against other technology and blockchain-related targets. After ARTEX was tied to attacks, the original project went private, but forks are still publicly available.
Security researchers have been warning about this trend for months. Earlier this year, Google’s threat intelligence team described how state-linked hackers are using AI to find and exploit weaknesses, with direct consequences for crypto security.
Why This Breach Matters
The Chainstack case shows that agentic tools do not need new exploits to cause damage. Every step in the attack path used a known configuration problem: a test server left on default credentials, an internal AI tool server with no login, and machine credentials that worked in both development and production. An automated framework can test those openings much faster than a human operator, so neglected test systems become a bigger risk.
The exposed data also creates follow-on risks for customers. How quickly password hashes can be cracked depends on the hashing method and on how strong each password is. That is why Chainstack is asking users to change their passwords on any other service where they used the same one. Names and work emails tied to a known infrastructure account are also useful for targeted phishing. Chainstack says it will never ask for passwords, tokens, or keys.
What Chainstack Customers Should Do Now
Chainstack recommends the following steps:
- Change your account password, and change it on any other service where you used the same password.
- Rotate node credentials with the self-service option in the console. Existing endpoints keep working until rotation is complete, so there is no downtime.
- Regenerate platform API keys if you use the Chainstack platform API.
- Watch for phishing. Treat any message asking for passwords, tokens, or keys as suspicious.
Chainstack says it detected and contained the intrusion on October 31 and has been hardening its systems since then. Its report includes IoCs and a full reconstruction of the attack path for security teams.
Also Read: Across Protocol Domain Hijacked via Namecheap Social Engineering Attack, Users to Be Made Whole
Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.


