<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>SignalPlus breached via fake Teams invite; Binance and Deribit revoke linked API keys · updates</title>
  <link>https://pwn.watch/i/signalplus-telegram-teams-social-engineering-api-keys-nov-2026</link>
  <description>Crypto options/derivatives terminal SignalPlus disclosed on Nov 5 2026 that attackers compromised an engineer through a fake Microsoft Teams invitation sent from a third-party vendor contact's hijacked Telegram account, then used that foothold against SignalPlus's internal network in the early hours of Nov 4. SignalPlus says total losses are under US$82,000, it is reimbursing affected users in full, and it has paused terminal services while it reviews security. As a precaution Binance and Deribit revoked all API keys linked to SignalPlus; both say their own systems were unaffected. SignalPlus acknowledges it had not made IP whitelisting mandatory for exchange API access. Users should manage positions on the exchanges directly and wait for SignalPlus before reconnecting API keys.</description>
  <language>en</language>
  <lastBuildDate>Thu, 05 Nov 2026 00:00:00 GMT</lastBuildDate>
  <atom:link href="https://pwn.watch/i/signalplus-telegram-teams-social-engineering-api-keys-nov-2026/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title>SignalPlus breached via fake Teams invite; Binance and Deribit revoke linked API keys: Binance announces it has removed all API keys linked to SignalPlus as a precaution; CZ urges users to revoke SignalPlus API keys on other exchanges too. Deribit also revokes SignalPlus-linked keys. Both say their own systems were unaffected.</title>
    <link>https://pwn.watch/i/signalplus-telegram-teams-social-engineering-api-keys-nov-2026</link>
    <guid isPermaLink="false">https://pwn.watch/i/signalplus-telegram-teams-social-engineering-api-keys-nov-2026#2026-11-05-4429e4f6</guid>
    <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;&lt;a href=&quot;https://x.com/binance/status/2118295116716589383&quot;&gt;Source&lt;/a&gt;&lt;/p&gt;</description>
  </item>
  <item>
    <title>SignalPlus breached via fake Teams invite; Binance and Deribit revoke linked API keys: SignalPlus publishes its incident response: losses under US$82k, full reimbursement underway, services paused, and admission that IP whitelisting was not mandatory for exchange API access.</title>
    <link>https://pwn.watch/i/signalplus-telegram-teams-social-engineering-api-keys-nov-2026</link>
    <guid isPermaLink="false">https://pwn.watch/i/signalplus-telegram-teams-social-engineering-api-keys-nov-2026#2026-11-05-b592ba0e</guid>
    <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;&lt;a href=&quot;https://x.com/SignalPlus_Web3/status/2118334759697068490&quot;&gt;Source&lt;/a&gt;&lt;/p&gt;</description>
  </item>
  <item>
    <title>SignalPlus breached via fake Teams invite; Binance and Deribit revoke linked API keys: Attacker uses a compromised third-party vendor Telegram account to send a SignalPlus engineer a fake Microsoft Teams invite, compromises the engineer machine, then pivots into SignalPlus's internal network; SignalPlus detects and contains the activity the same day and contacts exchange partners.</title>
    <link>https://pwn.watch/i/signalplus-telegram-teams-social-engineering-api-keys-nov-2026</link>
    <guid isPermaLink="false">https://pwn.watch/i/signalplus-telegram-teams-social-engineering-api-keys-nov-2026#2026-11-04-a8010de6</guid>
    <pubDate>Wed, 04 Nov 2026 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;&lt;a href=&quot;https://x.com/SignalPlus_Web3/status/2118334759697068490&quot;&gt;Source&lt;/a&gt;&lt;/p&gt;</description>
  </item>
</channel>
</rss>
