Skip to main content

    CybersecurityAnalysis

    Chainalysis breach by 'agentic' attacker widens: all users' password hashes and live tokens exposed

    Chainalysis disclosed on October 30 that an outside actor using 'offensive agentic techniques' reached internal systems. By November 4 the company said names, usernames, password hashes and live tokens for all users had been exposed.

    Sonomos NewsroomPublished 4 min read

    Chainalysis, the blockchain analytics company, said on October 30 that an outside actor using what it called "offensive agentic techniques" had gained unauthorized access to its systems and internal tools, and by November 4 it said the names, usernames, password hashes and live tokens of all its users had been exposed. The company has not said how the actor got in, how many users are affected, or what the agentic techniques were.

    The scope in Chainalysis's running incident notice grew across a week, so the first account and the current one differ materially.

    What did Chainalysis say on October 30?

    The original notice said the company had detected an external actor with access to its systems and internal tools, and described the incident as unrelated to the recent crypto theft involving Binance. Based on the evidence then available, it said no investigation content, clear-text passwords, MFA secrets or session tokens had been accessed. It said the accessed data was limited to user IDs, names, email addresses and role labels for users provisioned on the platform.

    BleepingComputer reported that the company was still determining which records were accessed for each organization, that it had not disclosed the entry point or how long the actor had access, and that it was patching vulnerabilities, working with outside security experts and using large language models in a wider security review of its platform. Help Net Security noted that exposed names and contact details raise the risk of social engineering.

    How did the account change between October 30 and November 6?

    According to the dated updates in Chainalysis's notice:

    DateWhat the notice said
    October 30Unauthorized access to systems and internal tools; user IDs, names, email addresses and role labels accessed; no evidence of access to investigation content, clear-text passwords, MFA secrets or session tokens
    November 2Reactor and Data Solutions taken offline pending third-party security assessments; compliance transaction monitoring products kept running under close monitoring
    November 4 (9:50 a.m. EST)An "on-path attack" exposed a subset of customer passwords; affected accounts locked and users told to reset passwords
    November 4 (10:30 a.m. EST)KYT, other address screening products and the login page taken offline after abnormal activity
    November 4 (11:00 p.m. EST)Names, usernames, password hashes and live tokens for all users exposed to a malicious actor; no evidence that investigations data was accessed or attribution data manipulated; customers whose KYT accounts appeared to be accessed without authorization notified directly
    November 6KYT and Address Screening restored in phases; customers asked to submit trusted IP addresses for an allowlist, and all users must reset passwords and rotate API keys, as applicable, before registering transactions

    The November 4 update therefore contradicts the October 30 statement that no tokens were accessed: it says live tokens for all users were exposed. Reactor and Data Solutions remained offline as of the latest update while systems were hardened with outside experts.

    What does "offensive agentic techniques" mean here?

    Chainalysis has not defined the phrase. Its notice does not say which tools or models the actor used, whether a prebuilt framework was involved, or how the actor first entered. BleepingComputer's report likewise says it is unclear whether the actor used an existing framework or custom agents, and the notice does not say whether the later "on-path attack" is connected to the original entry.

    The closest public reference point is a separate case. In a report published October 21, Microsoft attributed the ConnectWise supply chain compromise to Storm-0940, a China state-aligned actor, which it said used ARTEX, a multi-agent LLM penetration-testing framework, against hundreds of organizations since September. Microsoft reported that the actor attempted sign-ins to more than 2,250 tenants, that failed logons peaked at about 2,900 per minute on October 11, and that in several cases privileged cloud access followed less than three hours after initial targeting. No source we opened links the two incidents, and Chainalysis has not named an actor.

    What do the exposed data types mean for users?

    A password hash is not a clear-text password, and Chainalysis's notice says affected users must reset passwords and rotate API keys before registering transactions. The notice pairs the password reset with a request for trusted IP addresses for an allowlist. According to BleepingComputer, Chainalysis also warned of unexpected password-reset or authentication prompts and of scammers impersonating the company, and advised enabling two-factor authentication.

    The exposed fields (names, work email addresses, role labels) are the inputs to targeted phishing. For background on how AI agents can be steered by untrusted content, see what prompt injection is and AI agents and data privacy for the access risks agents create. For a related earlier case of AI systems acting beyond their authority, see our story on OpenAI's report of test models that bypassed access controls.

    What is still unresolved?

    • Entry point and timeline. Chainalysis has not said how the actor got in or how long it had access.
    • Number of users. The company has not said how many users or organizations are affected, and said it is still determining which records were accessed for each organization.
    • The agentic claim. The description rests on the company's own wording; no independent technical analysis was available in the sources we opened.
    • Product restoration. Reactor and Data Solutions were still offline in the latest update, and the company has promised more detail once its analysis is complete.

    Sources

    1. 1
      Security incident notice and updates (October 30 to November 6)

      Chainalysispublished read chainalysis.com

    2. 2
      Chainalysis discloses data breach from offensive agentic techniques

      BleepingComputerpublished read bleepingcomputer.com

    3. 3
      Chainalysis breached using offensive agentic techniques

      Help Net Securityread helpnetsecurity.com

    4. 4
      Storm-0940 uses ARTEX agentic AI in ConnectWise supply chain compromise

      Microsoft Security Blogpublished read microsoft.com

    How this story was checked

    Automated source check, . Each claim below was compared with the source it cites before publication. Read our standards for what that check does and does not cover.

    • Chainalysis said on October 30 that an external actor gained unauthorized access to its systems and internal tools, and that user IDs, names, email addresses and role labels were accessed. Source 1
    • On November 4 Chainalysis said names, usernames, password hashes and live tokens for all users had been exposed, with no evidence that investigations data was accessed. Source 1
    • Chainalysis has not said how the actor got in or what the agentic techniques were. Source 2
    • Microsoft reported that Storm-0940 used the ARTEX agentic framework against hundreds of organizations and attempted sign-ins to more than 2,250 tenants after the ConnectWise compromise. Source 4

    Tags: AI agents · Data breach · Incident disclosure · Prompt injection

    From the publisher

    Sonomos publishes this newsroom and makes Locke, a desktop app that detects sensitive data on your device and masks it before a prompt reaches an AI service.

    How Locke works

    General information about privacy, security and AI, not legal advice. Laws and guidance change; check the dates above and the sources cited before relying on anything here.