SignalPlus Reports Under $82,000 in Cyberattack Losses
The crypto trading platform says a breach detected November 4 traced to a compromised third-party Telegram account has cost it less than $82,000.
Updated on Nov. 6, 2026 in Cybersecurity
SignalPlus reported total losses of less than $82,000 from a cyberattack detected on November 4. The company said it has pledged full reimbursement to affected customers and revoked all linked API keys.
Why it matters
The incident affected some user accounts that lacked IP allowlisting, highlighting the risk that third-party account compromises pose to connected trading services. Users linked to the platform were told to check their accounts and wait for confirmation before reconnecting.
The company reported total losses below $82,000 from an attack detected November 4, traced to a compromised third-party Telegram account. Some accounts without IP allowlisting were affected, and the number of impacted users has not been disclosed.
The players
SignalPlus
SignalPlus is a crypto trading platform whose terminal and linked exchange API integrations were affected by the breach.
Binance
Binance is a major global cryptocurrency exchange that revoked SignalPlus API keys and issued account-check guidance to users.
The details
SignalPlus temporarily paused its terminal while responding to the breach and worked with exchange partners to revoke all API keys linked to its service. Binance revoked SignalPlus API keys and told users to check their accounts and wait for confirmation before reconnecting.
Timeline
November 4, 2026: Cyberattack detected against SignalPlus.
Coming days: SignalPlus expects to restore all services.
The Tech Race
The incident illustrates the risk that exchange API integrations pose when user accounts lack IP allowlisting, a control central to how major platforms like Binance secure linked trading tools. It underscores how third-party account compromises can propagate into crypto trading infrastructure.
Users with SignalPlus or Binance API links should check their accounts and wait for confirmation before reconnecting. Enabling IP allowlisting on connected accounts is the control that would have blocked access from unrecognized locations in this breach.
The takeaway
Securing third-party account logins and enabling IP allowlisting on exchange API keys are practical steps that limit the damage a single compromised account can cause. Users should verify their connected services before reconnecting after any platform pause.
Further reading
Explore more Cybersecurity coverage for related breach and account-protection stories.
Source note: This article includes information reported by TokenPost.
