← News

Coinigy suffers unauthorized access and recommends API key revocation on exchanges

Crypto asset management platform Coinigy suspended its operations after detecting an intrusion and recommended the immediate cancellation of API keys directly on linked exchanges.

By CyberX I.T SolutionsCibersegurança6 min readSource: Coinigy confirma invasão e alerta para risco de operações fraudulentas com chaves de API ↗Ler em português →

The crypto asset aggregation and trading platform Coinigy confirmed the occurrence of unauthorized access to its internal systems, detected on November 12, 2026. In response to the intrusion, the company preemptively took its services offline to enable digital forensics work and issued a formal statement aimed at mitigating residual risks for users. The alert focuses on the potential exposure of API keys and their respective cryptographic secrets provided by investors to integrate their accounts at third-party exchanges with the service interface.

According to the clarifications released so far, the notification measure is of a preventive nature. There is no consolidated record of confirmed mass exfiltration, consummated malicious use of credentials, or direct financial loss incidents reported by account holders. Despite the lack of confirmation of ongoing fraud, the company strongly recommended that all customers, including former users with inactive registrations, manually invalidate any access keys issued on external trading platforms.

The risk dynamics associated with delegating integration keys

Coinigy's operational model is based on portfolio centralization, allowing order placement and consolidated position monitoring through Application Programming Interface (API) keys issued by exchanges. These keys function as programmatic credentials that eliminate the need for continuous interactive authentication and master password entry. Depending on the scope configured at the time of issuance, the credential can authorize read-only analytical access to balances, active execution of buy and sell orders, or, in less recommended scenarios, direct transfer and withdrawal orders for assets.

The criticality of the incident stems from the persistence of credentials within the issuing systems. The act of disconnecting an application locally or even the complete shutdown of the intermediary's servers does not revoke tokens previously registered within the exchange ecosystem. Once granted, the authorization remains functional within the respective exchange's infrastructure until an explicit revocation command is issued by the account holder or a temporal expiration configured in the session policy occurs.

Even in circumstances where withdrawal permissions are disabled — standard practice for analytical tools —, credentials authorized exclusively for trading carry significant potential for harm. Attackers in possession of such credentials can orchestrate cross-trading operations in low-liquidity market pairs, intentionally skewing order books to divert financial volume to externally controlled accounts. Meanwhile, read-only keys, although unable to authorize transactions, expose asset holdings, portfolio composition, and trading strategies, expanding the attack surface for targeted social engineering attacks.

Required defensive actions and account containment

In light of the event, users must directly access the official portals of each integrated exchange and perform the permanent deletion of all keys previously configured for Coinigy. The process must be carried out manually and individually within the API management sections of each financial institution, given that resetting primary passwords for interactive access on the exchange or on the compromised platform itself does not automatically invalidate pre-existing application tokens.

In addition to invalidating access, auditing recent logs of open orders, execution history, withdrawal requests, and any changes to account security settings is recommended. If atypical activity is detected, technical guidance involves temporarily freezing the profile with the exchange's support team and retaining transaction IDs, timestamps, and addresses for forensic support. Coinigy further instructed that no new integration keys should be linked to its infrastructure until the completion of the forensic investigation confirms the environment's integrity.

Conceptual illustration of API keys with access permissions and revoked connection between platform and exchanges
Image: Minuto da Segurança da Informação

CyberX Technical Analysis

From a defensive security architecture perspective, the Coinigy incident exposes one of the most sensitive links in the delegated trust model within distributed custody and execution ecosystems. The aggregation of external credentials at a single centralized point creates an extremely high-value asset for threat actors: relational databases or storage mechanisms containing application secrets that enable proxy remote actions on third-party services.

Historically, the provider stated that it kept API secrets segregated in dedicated encrypted repositories. However, the lack of details regarding the vectoring of the incident makes it impossible to confirm whether the compromise reached master decryption keys, involved the extraction of parameters from volatile memory during microservices execution, or stemmed from the exploitation of flaws in backend APIs and cloud environments. The unauthorized retention or decryption of encrypted API keys fundamentally depends on the Key Management Services (KMS) architecture and the level of segregation between application servers and the storage instances of symmetric keys.

Another critical element lies in the widespread lack of origin restriction (IP Whitelisting) during the creation of keys intended for SaaS integration platforms. When an exchange allows trading keys to be issued without mandatory binding to the fixed IP address blocks of the hired service, the potential extraction of these key-secret pairs enables direct API calls from any infrastructure operated by malicious actors, bypassing additional perimeter containment layers.

CyberX SOC Intelligence Bulletin

The confirmed intrusion into Coinigy's infrastructure requires priority operational action aimed at identifying transactional anomalies and immediately remediating integration surfaces between local or corporate systems and virtual asset exchanges, regardless of the current absence of publicly executed malicious artifacts.

Exposure Conditions and Scope Assessment

Any exchange accounts that have issued API key pairs (Key ID and Secret) provided to Coinigy are vulnerable to the abuse scenario, regardless of the date the integration was performed. Operational risk is divided according to the privileges assigned to the credential:

  • Keys with Trading permission: Severe risk of market manipulation in low-liquidity order books and capital erosion via automated unfavorable trades.

  • Keys with Withdrawal permission: Critical risk of direct exfiltration of funds, although enabling this privilege usually requires manual confirmation outside the standard Coinigy workflow.

  • Keys with Read-Only permission: Risk of informational reconnaissance, enabling financial profiling of targets.

Investigation and Telemetry Audit Guidelines

Security teams and incident response analysts managing crypto-asset positions should execute the following defensive routines on the issuing platforms:

  • Extract and inspect authentication and API call logs on exchanges, filtering access by IP addresses not correlated with known Coinigy clusters or the organization's own addresses.

  • Audit the history of orders executed since November 12, 2026, with particular attention to trades with unusual spreads or involving currency pairs with very low trading volume.

  • Check recent changes to withdrawal permission lists (whitelisting of destination wallets) and modifications to two-factor authentication (2FA) factors.

Containment and Response Measures

Immediate response should not depend on additional notices from the vendor and requires the execution of the following procedures:

  • Summary revocation of 100% of API keys associated with the Coinigy service in the respective exchange control centers.

  • Temporary suspension of new key generation until the conclusion of Coinigy's forensic process and provision of a clean environment technical attestation.

  • Mandatory implementation, in future integrations with any third party, of strict source IP address restrictions on exchanges supporting this control.

  • No verifiable public indicators of compromise (IoCs), such as hashes, command-and-control domains, or specific signatures, have been identified in reports released to date.

Frequently Asked Questions

When did the security incident at Coinigy occur?

Unauthorized access to Coinigy's internal systems was detected on November 12, 2026.

What is the main recommendation for Coinigy users?

The recommendation is to manually access the official portals of each integrated exchange and perform the permanent deletion of all API keys previously configured for Coinigy.

Does resetting the exchange's main password invalidate API keys?

No, resetting primary interactive login passwords on the exchange does not automatically invalidate previously generated API credentials.

Do API keys without withdrawal permission also pose a risk?

Yes. Even without withdrawal permission, credentials authorized for trading allow attackers to execute cross-trades in low-liquidity pairs to manipulate order books.

Esta análise foi útil?

Ainda não há avaliações.