Close Menu
Chain Tech Daily

    Subscribe to Updates

    Get the latest creative news from FooBar about art, design and business.

    What's Hot

    Serpent upgrades: More Fun Stuff

    November 17, 2026

    Features, security, fees, and limitations

    November 17, 2026

    DAOs, DACs, DAs and More: An Incomplete Terminology Guide

    November 17, 2026
    Facebook X (Twitter) Instagram
    Chain Tech Daily
    • Altcoins
      • Litecoin
      • Coinbase
      • Crypto
      • Blockchain
    • Bitcoin
    • Ethereum
    • Lithosphere News Releases
    Facebook X (Twitter) Instagram YouTube
    Chain Tech Daily
    Home » Your crypto trading bot can lose money without withdrawal access
    Crypto

    Your crypto trading bot can lose money without withdrawal access

    James WilsonBy James WilsonNovember 17, 202622 Mins Read
    Facebook Twitter Pinterest LinkedIn WhatsApp Reddit Tumblr Email
    Share
    Facebook Twitter LinkedIn Pinterest Email



    SignalPlus says it reimbursed 23 users after an attack caused $81,897 in losses and prompted exchanges to cut its customer connections, drawing attention to the access traders give outside platforms that can buy and sell assets inside their accounts even when they have no permission to withdraw cryptocurrency to an external wallet.

    Summary

    • SignalPlus traced its Nov. 4 intrusion to a fake Microsoft Teams invitation sent through a vendor contact’s compromised Telegram account, after which the attacker used an engineer’s access to target the company’s internal network.
    • Binance and Deribit revoked SignalPlus-linked API keys as a precaution and directed customers to manage their accounts through the exchanges, while both said their own systems had not been affected by the reported issue.
    • Disabling withdrawals restricts one way funds can leave an account, but a connection authorized to trade can still change its holdings, incur fees and open positions that lose money as market prices move.
    • SignalPlus acknowledged that it had not required IP whitelisting for exchange API access and subsequently announced tighter access requirements, employee-device protections and internal controls as part of its response.
    • The company said on Nov. 8 that it had completed reimbursement within 72 hours of detecting the attack, while its investigation and security upgrades continued ahead of a planned phased restoration of services.

    The attack began outside the exchanges where SignalPlus customers held their money. According to the trading platform, an intruder compromised an engineer’s computer and later used the employee’s privileges to reach its internal network.

    Exchange partners disabled the credentials connecting SignalPlus to customer accounts, and the company paused its services. Customers could still sign in at the exchanges, but the trading, monitoring and automation previously handled through SignalPlus were interrupted.

    The response left users needing to check what had already happened inside their accounts. Cutting off an outside platform prevents further requests through the revoked keys; orders accepted by an exchange and positions opened before the shutdown still need to be managed there.

    JUST IN: Binance revokes all API keys linked to SignalPlus after reported security issue

    CZ has urged users to revoke SignalPlus API keys across other exchanges as well, warning against sharing exchange credentials with third-party platforms. pic.twitter.com/kEWyofhaF9

    — crypto.news (@cryptodotnews) November 5, 2026

    A vendor contact’s account led the attacker to an engineer

    SignalPlus detected unusual activity in the early hours of Nov. 4 and began investigating an intrusion into its systems. The company later said the attacker had first approached an engineer using a Telegram account belonging to a contact at one of its technology vendors.

    The account had been compromised. Posing as the vendor contact, the attacker sent the engineer a fake Microsoft Teams meeting invitation, according to SignalPlus’s account of the incident.

    The invitation led to the engineer’s computer being compromised. The intruder remained on the machine before using the employee’s access privileges to attack the internal network on Nov. 4, the company said.

    As crypto.news reported when SignalPlus disclosed the attack, the team said it blocked the intrusion, closed identified vulnerabilities and contacted its exchange partners. It also put its services into maintenance while reviewing the security of its systems.

    SignalPlus provides infrastructure for cryptocurrency options and derivatives trading. Its customers use the platform to monitor and manage activity across exchanges, with API connections allowing the software to act on their accounts.

    Those connections meant the company’s response could not end with isolating the engineer’s computer. SignalPlus also needed the exchanges to disable the credentials through which its platform could submit customer requests.

    An API key is issued by an exchange and carries permissions chosen for the connection. A trading platform uses it to authenticate requests without asking the customer to log in and approve every order individually.

    The customer’s exchange password does not have to be shared with the platform for that arrangement to work. The key supplies another authorized way into account functions, including trading where that permission has been enabled.

    The attack therefore reached a company that customers had entrusted with part of their account management. The assets could remain at an exchange while the service handling instructions for those assets was dealing with an intrusion.

    SignalPlus said its precautions covered all connected users, including accounts where it had not found unusual activity. The shutdown was intended to remove access while the investigation proceeded, rather than wait for a loss report from every customer.

    In its initial statement, the company estimated losses below $82,000 and said reimbursements had begun. It asked users who believed they had been affected to contact its team for verification.

    Exchanges cut the connections and sent users back to their accounts

    Binance announced on Nov. 5 that it had removed all API keys linked to SignalPlus after the third-party platform reported a potential security issue. The exchange said its own systems were unaffected and customer funds remained safe.

    The Binance key-removal notice also told customers to review trading positions and open orders directly on the exchange. Users were advised to wait for SignalPlus to confirm that the issue had been resolved before reconnecting their accounts.

    Deribit revoked the linked keys as well. It said its investigation had found no indication that its own systems or data had been affected, while warning customers that SignalPlus trading, monitoring and automation would stop working.

    The exchanges were withdrawing the authority previously given to the outside service. Their account systems remained available, allowing customers to inspect balances and manage exposure without waiting for the SignalPlus interface to return.

    Binance founder Changpeng Zhao extended the warning to users with connections elsewhere. He urged SignalPlus customers to revoke their keys on other exchanges and advised against storing API keys with third-party platforms.

    A customer using one interface for several exchanges can have several separate credentials behind it. Removing a Binance key does not itself remove a key issued by another venue, so the response required attention to each connected account.

    SignalPlus said it contacted all partner exchanges and sought the suspension of every associated key. Its platform services were paused at the same time, interrupting the normal interface through which customers managed those accounts.

    The distinction mattered for users who had not suffered a loss. They could still experience a service interruption because the precautionary action applied to their connection as well as to accounts identified as affected.

    The company said disabling a key did not mean the corresponding account information or assets had necessarily been compromised. Its response removed access across the service while the investigation established the affected cases.

    Binance’s instruction to inspect those orders addressed what key removal alone could leave behind. An accepted instruction belongs to the exchange’s order system, and removing the credential that submitted it is not the same operation as canceling that instruction.

    Trading permission can still put the balance at risk

    The separation between trading and withdrawals is built into exchange API settings. A customer can authorize software to place orders while refusing permission to send cryptocurrency out of the account.

    Kraken’s API-key setup guide gives a third-party trading service as an example. It says such a service would need order permissions but “would almost certainly not require Withdraw Funds permission.”

    The exchange can therefore reject a withdrawal request while accepting a purchase or sale from the same connection. The assets stay within its custody, but the trading software can change what the customer owns.

    Coinbase Exchange’s permission settings make the separation explicit too. Trade allows orders and data access, while Transfer allows movements of value, including withdrawals.

    A losing trade needs no external transfer. A bot can buy an asset whose price falls, sell an asset before it rises or build a position that becomes expensive to unwind.

    Trading also incurs execution costs. Orders can cross a spread, consume available liquidity at different prices and generate exchange fees, reducing the account’s value even when the strategy produces some profitable trades.

    Repeated transactions increase the amount on which fees are charged. The same deposit can be used for many purchases and sales, so the total trading volume can substantially exceed the funds originally allocated to the bot.

    A strategy can also finish with more units of a token while leaving the customer with less value in dollars. The token count alone does not establish whether the account gained or lost money over the period.

    Where the account permits leveraged products, trading access can expose it to margin requirements and liquidation. The consequences depend on the products and balances the credential is allowed to use, rather than whether it can send funds to a blockchain address.

    Unauthorized trading adds another risk to ordinary strategy losses. An attacker able to use a trading credential can submit orders under the authority already granted to that connection.

    The exchange then receives a request carrying valid authentication, even though the account owner did not intend that particular trade. Restrictions on withdrawals do not tell the exchange whether an otherwise permitted purchase is consistent with the customer’s strategy.

    A trading bot’s advertised allocation is also not necessarily a restriction enforced by the exchange. If the key can access more of the account, the software may be responsible for respecting the smaller amount shown on its dashboard.

    The customer needs to distinguish the balance assigned inside the service from the portfolio or subaccount actually exposed to its credential. A setting in an outside application can be lost with that application’s controls, while an exchange-side restriction applies to requests received at the venue.

    Earlier API incidents also involved unwanted trades

    The SignalPlus incident followed earlier disputes over trading credentials held by outside platforms. In 2022, customers of trading-bot service 3Commas reported unauthorized activity in connected exchange accounts.

    An October 2022 report covered an FTX customer’s claim of thousands of unwanted trades involving the DMG token. The customer said assets had been lost through activity conducted using a 3Commas-linked API connection.

    The initial explanations were disputed. The report recorded conflicting positions from FTX and 3Commas over how the credential had been exposed, as users sought an explanation for orders they said they had not authorized.

    The complaints concerned what had happened through the trading account. They drew attention to losses that could occur through execution rather than a straightforward transfer to an attacker’s external wallet.

    Later that year, 3Commas issued updates on the API-key investigation. The controversy expanded from individual customer complaints to questions about credentials used across several exchanges.

    By late December, 3Commas acknowledged the validity of keys published by a hacker after earlier disputing claims about an exposure. Customers were told to address the credentials connected to their exchange accounts.

    OKX said it had taken protective action and would continue supporting the platform. As crypto.news reported in its coverage of the exchange’s response to the 3Commas leak, OKX deployed transaction monitoring and refreshed API keys for affected users.

    The events belong to the 2022 incident, not the SignalPlus investigation. They show the practical response exchanges have used when credentials entrusted to another company become a security concern: restrict the connection and examine activity already conducted through it.

    An exchange can hold the assets securely while a customer-authorized service misuses its trading authority or loses control of that authority. Those risks arise from different parts of the arrangement, which is why the exchange’s own system status does not resolve every concern about the connection.

    A withdrawal history alone would miss those changes. It can show that no coins left through a withdrawal without explaining why an account now holds different assets or is worth less than it was before.

    For a reported API incident, the key’s permissions and order records provide the connection between the access granted and the financial result. The provider’s investigation then needs to establish how that access was obtained and used.

    SignalPlus accepted responsibility for a missing safeguard

    SignalPlus acknowledged that it had not made IP whitelisting mandatory for exchange API access. The accounts identified as affected lacked that restriction, according to the company’s initial account.

    “We take responsibility for this oversight,” the company said in its Nov. 5 statement. It included tighter API access requirements among the changes planned after the intrusion.

    An IP restriction limits the internet addresses from which a credential can be used. A copied key presented from an unapproved address can be rejected even when the supplied authentication would otherwise be valid.

    The control is applied to the API connection, rather than to a withdrawal destination. It restricts where requests originate, while a withdrawal address list restricts where an authorized transfer may send funds.

    Kraken includes IP restrictions and an expiry setting among its API-key options. Coinbase Exchange requires an IP whitelist when creating a key for the documented product, alongside the permissions and portfolio chosen by the customer.

    The restriction needs to match the service’s actual infrastructure. A provider submitting requests from addresses outside the approved list can lose access, so its connection instructions need to identify the addresses customers are being asked to authorize.

    The control also leaves the approved systems needing protection. If an intruder operates through infrastructure already on the list, an address check alone does not establish that the request came from the legitimate operator.

    SignalPlus’s announced changes therefore covered more than the whitelist. The company also named development-device security, internal access controls and key management as areas it would strengthen.

    The engineer’s compromised computer made those internal controls directly relevant to its account of the attack. The company said the intruder used employee privileges against the network before the team detected and contained the activity.

    The keys used by customers also sit within the provider’s own security arrangements once supplied to it. Storage, staff access and the systems allowed to submit requests become part of the customer’s exposure to that company.

    Kraken’s API-security guidance treats the credentials as sensitive account access. Its advice covers the public key, private key and QR code, which can contain information used to authorize requests.

    Sharing a setup screenshot can expose that information outside the intended service. An owner who covers a text field but leaves the credential’s QR code visible may still disclose the material needed to use the connection.

    SignalPlus also said it would expand cooperation and threat-intelligence sharing with exchanges, technology partners and security firms. Its response combined changes to customer connections with work on the employee systems through which the intrusion began.

    Revoking a key leaves completed trades in place

    The exchange response stopped further requests through the revoked SignalPlus credentials. It did not erase trades already executed or automatically determine what customers should do with positions remaining in their accounts.

    An open limit order can stay at an exchange after the software that submitted it disconnects. If the market later reaches the order’s price, the instruction can execute unless it has been canceled or otherwise expired under the venue’s rules.

    A completed purchase leaves the customer holding the asset, and that asset’s price can continue moving. A derivatives position can continue gaining or losing value and remain subject to the exchange’s margin requirements after the external interface has stopped operating.

    Binance’s direction to review positions and orders through its own platform addressed that continuing exposure. Customers needed to see the exchange’s current records rather than assume the bot’s interruption had closed their trades.

    Order status also matters when execution was partial. The exchange may have filled part of an instruction while retaining the rest, leaving both an acquired position and an outstanding order for the owner to review.

    A bot’s dashboard can be out of date if its connection failed before it received the final update. The exchange’s fill record establishes what actually traded, and its open-order list shows what remains pending.

    Some venues provide tools intended to cancel orders when an automated client stops responding. Kraken’s derivatives outage guidance describes a timed cancellation function often called a dead-man’s switch.

    The client renews a timeout while operating. If it fails to send another request before the period ends, the exchange cancels the orders covered by the function.

    Cancellation removes pending instructions. It does not reverse a completed fill, return the account to its earlier holdings or close every position that was already open before the interruption.

    The location of a stop-loss instruction matters for the same reason. An order accepted by the exchange can remain there, while a rule held only inside disconnected software depends on that software being able to send the next request.

    Customers returning to direct exchange management need to establish which orders were actually accepted. A stop-loss label on the external dashboard is not itself confirmation that the venue holds an instruction at the displayed level.

    A replacement connection can also encounter the orders and positions left by the previous one. Reviewing the account before restarting automation avoids giving new software an account state different from the one the customer expects it to manage.

    Account settings determine how much access a service receives

    The SignalPlus response required action on exchange-issued credentials, even though the intrusion began elsewhere. Those credentials define the functions an outside service can perform and the accounts or portfolios it can reach.

    Coinbase Exchange says an API key is limited to one portfolio. A user can therefore separate the portfolio used by a trading connection from other portfolios, subject to the product’s transfer and account rules.

    That can restrict the assets directly available to the connected software. It differs from entering an allocation inside the bot while leaving the underlying key authorized to trade a larger balance.

    The same review needs to include margin and funding permissions. A balance isolated on one screen should not be treated as a complete limit on exposure if other account resources can support positions or be moved into reach.

    Read-only services require less authority than execution software. A reporting tool can retrieve balances and history without needing to place orders, while a trading service needs order permissions to perform the work the customer requested.

    Kraken distinguishes public market data from private account endpoints. Displaying public prices does not require a customer key, while retrieving account information or trading on the customer’s behalf requires the relevant access.

    Sign-in security and API security also have separate settings. A customer can protect an interactive login with a password and second factor while an automated connection continues authenticating requests with its own credentials.

    Kraken provides additional two-factor authentication for API keys, subject to support from the client using them. Coinbase Exchange’s permission table says its Transfer permission can bypass 2FA.

    Expiry can end a key’s authority after a defined period. It can also interrupt a service still managing open positions, making the expiry date relevant to how the account will be handled when automation stops.

    Coinbase’s key-rotation instructions call for revoking the existing key, creating a replacement with only necessary permissions and updating the applications that use it. Issuing a new key without retiring the old one would leave an additional credential to manage.

    Kraken’s third-party integration guidance likewise directs users to the exchange’s key settings. A canceled subscription or deleted application is not evidence that the exchange has removed the authority previously granted to it.

    SignalPlus reported repayments while security work continued

    SignalPlus initially promised full reimbursement and said it had started verifying affected cases. In a Nov. 8 update, the company said all 23 identified users had been reimbursed within 72 hours of its detection of unusual activity on Nov. 4.

    It put the total affected amount at $81,897. The update followed the earlier estimate of losses below $82,000 and described the repayments as complete for those identified users.

    The company said it contacted customers while the security investigation was underway and worked with exchange partners on the response. It also invited anyone who believed they had been affected to contact official support for a review of transaction records.

    The payment update did not end the security work. SignalPlus said its team was continuing the investigation and strengthening API access requirements, whitelist verification, employee-device security and internal controls before progressively restoring services.

    The company said the shutdown had applied to every associated account regardless of whether anomalous activity was found. Customers outside the reimbursed group could therefore still have had their access interrupted by the precautionary suspension.

    For customers checking a claim, the exchange records establish the transactions and positions in the account. Those records can be compared with the provider’s assessment without relying on an external dashboard that may have stopped updating during the interruption.

    Repayment also needs to be kept separate from the trading result after the incident. A customer can receive compensation for identified unauthorized activity while still holding positions whose prices move before they are closed.

    SignalPlus’s statement described the amount it reimbursed and the users it identified. Customers seeking a further review were directed to submit their records through the company’s official support process.

    Its planned restart required another change to customer access. Binance’s earlier notice had advised users to wait for confirmation that the issue was resolved before reconnecting API keys and recommended IP restrictions when setting up a connection.

    In its Nov. 8 statement, SignalPlus said services would return progressively after system reviews and security upgrades were complete. The company said the restoration schedule and operating instructions would be published through its official channels once confirmed.

    What to Watch

    • Service restoration: SignalPlus’s dated notices confirming which functions have resumed, the security checks completed and the instructions customers must follow before creating replacement exchange connections.
    • Account review: Any further affected users or revised loss figures identified through transaction checks, alongside the company’s reported reimbursement of $81,897 to 23 users within 72 hours.
    • API requirements: How mandatory IP verification, permissions and credential handling change when customers reconnect, including the specific safeguards enforced by each exchange rather than only by the outside platform.
    • Outstanding positions: Orders, partial fills and market exposure remaining at the exchange after a key is revoked, especially where an interrupted service previously handled monitoring or stop-loss instructions.
    • Investigation findings: Further details from SignalPlus about the engineer compromise, employee access and internal controls, with findings attributed to the company or the investigators publishing them.

    FAQs

    Can a trading bot lose money when withdrawals are disabled?

    Yes. Trading permission can allow the bot to buy and sell assets inside an exchange account even when it cannot send cryptocurrency to an external address. Losing trades, execution costs and fees can reduce the balance, while leveraged products can expose it to margin requirements and liquidation. Disabled withdrawals restrict a funding action; the scope of trading still depends on the products, portfolios and permissions available to the key.

    What did SignalPlus say caused its intrusion?

    The company traced the attack to a technology-vendor contact’s compromised Telegram account. An attacker impersonated the contact and sent an engineer a fake Microsoft Teams invitation, compromising the engineer’s computer before using employee privileges against the internal network on Nov. 4. SignalPlus said it detected and contained the activity, contacted exchange partners to disable connected keys and paused its services while reviewing security and the affected customer accounts.

    Did Binance and Deribit say they had been hacked?

    Both exchanges revoked SignalPlus-linked API keys as a precaution. Binance said its own systems were unaffected, while Deribit said its investigation found no indication its systems or data had been affected. The action removed the outside service’s account access and interrupted its trading and monitoring functions. Customers retained direct access through the exchanges and were told to review positions and open orders there rather than wait for the external interface.

    How much did SignalPlus reimburse?

    SignalPlus said on Nov. 8 that it had reimbursed all 23 users it identified as affected, totaling $81,897, within 72 hours of detecting unusual activity on Nov. 4. Its first statement had estimated losses below $82,000 and promised full repayment. The later update said security work was continuing and invited users seeking an additional transaction review to contact official support. Those amounts and completion claims are the company’s account.

    Why did the missing IP restriction matter?

    An IP restriction lets an exchange reject requests made from addresses outside the approved list. SignalPlus acknowledged that it had not made the safeguard mandatory and said the affected accounts lacked it. The control can limit where a copied credential works, but the approved systems still need protection. SignalPlus’s response also included changes to employee devices, internal access and key management, addressing the intrusion alongside the customer connections.

    Does revoking a key close positions and cancel orders?

    Key revocation removes the credential’s authority to make further requests. It does not reverse completed trades, and customers need to check whether accepted orders remain open at the exchange. Positions already created can continue gaining or losing value after the bot disconnects. Binance specifically directed SignalPlus users to inspect their positions and orders through its own platform, where they could manage exposure during the interruption to the third-party service.

    Does login two-factor authentication cover the API connection?

    The connection uses its own credentials and the authentication rules of the exchange product. Automated orders do not necessarily generate the phone prompt used for an interactive login. Some exchanges provide additional API-specific authentication, with compatibility requirements for the software using it. Customers should check those settings alongside the key’s permissions and IP restrictions, and verify which credentials remain active at the exchange after removing an application or ending a subscription.

    Does restricting the key make a bot’s strategy safe?

    Permissions limit what software is authorized to do, but they do not prevent an authorized strategy from losing money. Holdings can fall in value, fees can accumulate and an order may execute at a worse price than expected. Exchange records show the completed trades and remaining exposure, including positions a dashboard’s profit figure may omit. Access restrictions should be assessed separately from investment performance. This is educational analysis, not investment advice.

    Disclaimer: This article is for information and educational purposes only and does not constitute financial or investment advice. Figures reflect regulatory filings and reporting available at the time of writing and change with each disclosure. Nothing here is a recommendation to buy, sell, or hold any security or asset. Always do your own research. Information is accurate as of Nov. 17, 2026. Legal and tax questions should be discussed with qualified professionals.





    Source link

    Share. Facebook Twitter Pinterest LinkedIn WhatsApp Reddit Tumblr Email
    James Wilson

    Related Posts

    Crypto November 17, 2026

    Features, security, fees, and limitations

    Crypto November 17, 2026

    Russia opens Bitcoin, Ethereum, USDT access to retail investors under new rules

    Crypto November 17, 2026

    Binance’s He Yi explains AI Pro transfers after hack-day withdrawal claims

    Crypto November 17, 2026

    Evernorth writes down pre-listing XRP holdings by 60% to $342 million

    Crypto November 17, 2026

    Bitcoin price falls for six straight weeks as bulls defend $62,000

    Crypto November 17, 2026

    What do its transaction totals show?

    Leave A Reply Cancel Reply

    Don't Miss
    Ethereum November 17, 2026

    Serpent upgrades: More Fun Stuff

    Over the past two weeks our primary focus has been getting all of the clients…

    Features, security, fees, and limitations

    November 17, 2026

    DAOs, DACs, DAs and More: An Incomplete Terminology Guide

    November 17, 2026

    Russia opens Bitcoin, Ethereum, USDT access to retail investors under new rules

    November 17, 2026
    Stay In Touch
    • Facebook
    • Twitter
    • YouTube
    • LinkedIn
    Our Picks

    Serpent upgrades: More Fun Stuff

    November 17, 2026

    Features, security, fees, and limitations

    November 17, 2026

    DAOs, DACs, DAs and More: An Incomplete Terminology Guide

    November 17, 2026

    Russia opens Bitcoin, Ethereum, USDT access to retail investors under new rules

    November 17, 2026

    Subscribe to Updates

    Get the latest creative news from SmartMag about art & design.

    Don't Miss
    Ethereum November 17, 2026

    Serpent upgrades: More Fun Stuff

    Over the past two weeks our primary focus has been getting all of the clients…

    Features, security, fees, and limitations

    November 17, 2026

    DAOs, DACs, DAs and More: An Incomplete Terminology Guide

    November 17, 2026

    Russia opens Bitcoin, Ethereum, USDT access to retail investors under new rules

    November 17, 2026

    Subscribe to Updates

    Get the latest creative news from SmartMag about art & design.

    Stay In Touch
    • Facebook
    • Twitter
    • Pinterest
    • Instagram
    About Us
    About Us

    ChainTechDaily.xyz delivers the latest updates and trends in the world of cryptocurrency. Stay informed with daily news, insights, and analysis tailored for crypto enthusiasts.

    Our Picks
    Lithosphere News Releases
    X (Twitter) Instagram YouTube LinkedIn
    © 2026 Copyright

    Type above and press Enter to search. Press Esc to cancel.