BTC $75,786.61 +0.90%
ETH $2,240.27 +1.13%
BNB $693.71 +0.08%
XRP $1.14 -1.60%
SOL $89.63 -0.94%
TRX $0.3192 +0.40%
DOGE $0.0716 -1.35%
ADA $0.1821 -2.52%
BCH $258.31 -2.61%
LINK $10.87 -0.26%
HYPE $77.64 -1.05%
AAVE $131.69 +0.25%
SUI $0.8581 -1.05%
XLM $0.1517 -1.65%
ZEC $1,264.02 -6.41%
AAPL $342.79 -0.28%
AMZN $259.91 -1.37%
GOOGL $285.45 -1.23%
MSFT $531.79 -0.49%
META $612.91 -1.19%
NVDA $188.03 -2.24%
TSLA $359.00 -0.42%
SNDK $834.05 -4.12%
INTC $56.07 +0.90%
SPCX $134.91 +2.27%
MU $689.45 -2.09%
AMD $446.17 -0.86%
BTC $75,786.61 +0.90%
ETH $2,240.27 +1.13%
BNB $693.71 +0.08%
XRP $1.14 -1.60%
SOL $89.63 -0.94%
TRX $0.3192 +0.40%
DOGE $0.0716 -1.35%
ADA $0.1821 -2.52%
BCH $258.31 -2.61%
LINK $10.87 -0.26%
HYPE $77.64 -1.05%
AAVE $131.69 +0.25%
SUI $0.8581 -1.05%
XLM $0.1517 -1.65%
ZEC $1,264.02 -6.41%
AAPL $342.79 -0.28%
AMZN $259.91 -1.37%
GOOGL $285.45 -1.23%
MSFT $531.79 -0.49%
META $612.91 -1.19%
NVDA $188.03 -2.24%
TSLA $359.00 -0.42%
SNDK $834.05 -4.12%
INTC $56.07 +0.90%
SPCX $134.91 +2.27%
MU $689.45 -2.09%
AMD $446.17 -0.86%

attack

All
Article
Flash

SignalPlus: The network attack originated from a third-party Telegram account being hacked, resulting in a loss of less than $82,000, and full compensation will be provided

The cryptocurrency derivatives trading tool platform SignalPlus announced that it was attacked in the early hours of November 4, originating from a third-party Telegram account that was hacked, affecting a small number of accounts that had not enabled IP whitelisting.The team stated that they quickly identified and controlled the intrusion. As a precautionary measure, they have revoked all associated API keys with their centralized trading platform partners and temporarily suspended terminal services. The official statement indicated that the total loss was less than $82,000, and affected users will receive full compensation. They expect to fully restore services in the coming days, with subsequent updates and operational guidelines to be released through official channels.This evening, Binance also issued a statement indicating that it has taken precautionary measures regarding the potential security issues reported by the third-party platform SignalPlus, actively revoking all API keys associated with SignalPlus.Binance emphasized that its own system was not affected and that user funds are secure. Binance reminded SignalPlus users to log directly into their Binance accounts to check their positions and open orders, and not to rebind API keys until the issues with SignalPlus are completely resolved. They also advised to always enable IP whitelisting.

GCSA disclosed KuCoin phishing, Bitkub supply chain risks, and Avalanche contract vulnerabilities: attackers transferred approximately 1,013,400 USDC

According to GCSA monitoring, the Global Cybersecurity Alliance (GCSA) has released three independent technical investigation reports, disclosing several recent security risks related to digital assets. Attackers impersonated security@ku.com to lure users into downloading remote control programs. GCSA found that the relevant domain names had not previously configured DMARC; after notification, KuCoin has completed rectification and enabled DMARC isolation policies.After the original MCP toolkit referenced in Bitkub's official documentation was taken down, a third party re-registered the npm package name. The installation method without a fixed version and the risk of plaintext keys may lead to credential leakage; there is currently no actual evidence of theft, and Bitkub has not yet responded to the notification.The TranchePool treasury within the Avalanche ecosystem was attacked due to a cross-day settlement logic flaw, where attackers utilized flash loans and repeated withdrawals to transfer approximately 1.0134 million USDC within 202 seconds. This incident is categorized as a vulnerability in the upper application, and the underlying network was not affected. GCSA stated that it has reported the clues to the relevant platforms and published the original analysis and evidence for industry reference.

GitBook Security Incident Review: Attack Targeting Trade.xyz, SSO Vulnerability Leads to Production Environment Breach

GitBook released a security incident review on November 2, stating that attackers exploited a vulnerability in its single sign-on process to forge employee login sessions, allowing them to query improperly configured GitHub App authentication information within the organization, access internal code repositories, and obtain Cloudflare API keys, ultimately gaining full production environment permissions through service accounts.GitBook disabled the relevant internal service accounts to cut off the attack within hours, resulting in the platform being offline for approximately 16 hours, and fully restored on November 3 at 11:56 UTC. The attackers remained in the production environment for a total of about 3 hours and 25 minutes. GitBook has rotated all infrastructure and revoked customer keys and API tokens.GitBook stated that current indications show the attack targeted a single customer rather than the platform as a whole, and no other customer content has been found to be tampered with. However, since the attackers could access customer data within the platform, they are treating it as if all customer data may have been exposed, including API tokens, integration keys, session signing keys, assistant Q&A records, and authorized repository permissions for GitHub and GitLab applications. Billing information, passwords, and IP addresses were not affected.GitBook noted that the speed and precision of the attack heavily relied on automation and AI. Slow Mist's Chief Information Security Officer 23pds forwarded the review, stating that the targeted entity was Trade.xyz. Trade.xyz previously indicated that the document anomaly stemmed from an intrusion into GitBook's infrastructure, and there were no signs of their own infrastructure being compromised, and they will migrate away from GitBook within a few days.
app_icon
ChainCatcher Building the Web3 world with innovations.