Binance Square

cryptosecurity

8.8M views
13,097 Discussing
White_Fang
·
--
On Sunday we asked why a 2024 Keystone order was still on file when the company's own policy says buyer data gets erased after 180 days. Keystone has now answered, and the answer came with a bigger problem. The attacker who got into its website on Oct 20 also took the key Keystone uses to check that a device is genuine. That key is written into each wallet at the factory and can't be erased or rewritten. With it, someone could build a counterfeit that passes Keystone's own authenticity check. So the company is destroying 18,835 devices in its inventory, has paused website shipments and is moving sales to preorders with a new key. On the data side, Keystone's store held 51,083 buyer records. 25,119 had been deleted under the 180-day rule. The other 25,964, from 2024 to 2026, may have been taken: names, contact details, shipping addresses and order details. Keystone says its automated erasure tool failed and nobody caught it. Another 12,873 unpaid checkout records may also be exposed. Recovery phrases, private keys and payment details were not, per Keystone. What that means if you own one: a Keystone delivered before Oct 20 is fine if it passes the check. One delivered after Oct 20 needs a direct check with Keystone support, even if it passes. You don't need to move your $BTC because of this alone, the company says. Keystone also says it will never ask you to ship a device back, so any "recall" email, call or parcel is a scam. #CryptoSecurity #HardwareWallet NFA. DYOR.
On Sunday we asked why a 2024 Keystone order was still on file when the company's own policy says buyer data gets erased after 180 days. Keystone has now answered, and the answer came with a bigger problem.

The attacker who got into its website on Oct 20 also took the key Keystone uses to check that a device is genuine. That key is written into each wallet at the factory and can't be erased or rewritten. With it, someone could build a counterfeit that passes Keystone's own authenticity check. So the company is destroying 18,835 devices in its inventory, has paused website shipments and is moving sales to preorders with a new key.

On the data side, Keystone's store held 51,083 buyer records. 25,119 had been deleted under the 180-day rule. The other 25,964, from 2024 to 2026, may have been taken: names, contact details, shipping addresses and order details. Keystone says its automated erasure tool failed and nobody caught it. Another 12,873 unpaid checkout records may also be exposed. Recovery phrases, private keys and payment details were not, per Keystone.

What that means if you own one: a Keystone delivered before Oct 20 is fine if it passes the check. One delivered after Oct 20 needs a direct check with Keystone support, even if it passes. You don't need to move your $BTC because of this alone, the company says. Keystone also says it will never ask you to ship a device back, so any "recall" email, call or parcel is a scam.

#CryptoSecurity #HardwareWallet
NFA. DYOR.
·
--
Bearish
🛡️ Rule #1 of Crypto: Protect Your Capital! In the $crypto world, security and risk management are far more important than chasing quick pumps. 💡 Quick Tips for Daily Traders: • Always enable 2FA on your accounts. • Never FOMO into a green candle without a plan. • Keep long-term holdings in a secure wallet. 💬 What is the biggest lesson you've learned in your crypto journey so far? Share your thoughts! 👇 #CryptoSecurity #TradingTips #BinanceSquare #HODL
🛡️ Rule #1 of Crypto: Protect Your Capital!
In the $crypto world, security and risk management are far more important than chasing quick pumps.
💡 Quick Tips for Daily Traders: • Always enable 2FA on your accounts. • Never FOMO into a green candle without a plan. • Keep long-term holdings in a secure wallet.
💬 What is the biggest lesson you've learned in your crypto journey so far? Share your thoughts! 👇
#CryptoSecurity #TradingTips #BinanceSquare #HODL
·
--
Bearish
Initia Pauses Network After Security Incident ⚠️ $INIT paused its network after a security vulnerability reportedly allowed an attacker to move about $2.7 million in assets. The team is working on a fix and investigating the incident. It’s a reminder to follow official updates and stay cautious during security events. Avoid unverified links or recovery claims. What matters most now is a secure fix and transparent updates. #Initia #INIT #CryptoSecurity #blockchain {future}(INITUSDT)
Initia Pauses Network After Security Incident ⚠️

$INIT paused its network after a security vulnerability reportedly allowed an attacker to move about $2.7 million in assets. The team is working on a fix and investigating the incident.

It’s a reminder to follow official updates and stay cautious during security events. Avoid unverified links or recovery claims.

What matters most now is a secure fix and transparent updates.

#Initia #INIT #CryptoSecurity #blockchain
We need to count words. Let's draft. Potential text: "Every time you connect a wallet to a DeFi protocol you expose its private keys to smart‑contract code you cannot fully audit. A single vulnerable contract or a malicious upgrade can drain the entire balance. Keeping your main holdings in a separate, offline wallet limits the blast radius — only the funds you intentionally move into a hot wallet are at risk. Three steps to protect yourself: 1. Create a dedicated hot wallet (hardware or reputable mobile app) used only for DeFi. Never store long‑term savings there. 2. Transfer only the amount you need for a specific interaction, then move any leftovers back to your cold storage immediately. 3. Regularly review and revoke token allowances with a tool like Revoke.cash; stale approvals are a common attack vector. Treat your DeFi wallet like a disposable cash envelope — load it, use it, empty it. Share this with someone new to crypto — it could save them! #Bitcoin #BTC #CryptoSecurity #StaySafe" Now count words. Let's count manually. "Every(1) time2 you3 connect4 a5 wallet6 to7 a8 DeFi9 protocol10 you11 expose12 its13 private14 keys15 to16 smart‑contract17 code18 you19 cannot20 fully
We need to count words. Let's draft.

Potential text:

"Every time you connect a wallet to a DeFi protocol you expose its private keys to smart‑contract code you cannot fully audit. A single vulnerable contract or a malicious upgrade can drain the entire balance. Keeping your main holdings in a separate, offline wallet limits the blast radius — only the funds you intentionally move into a hot wallet are at risk.

Three steps to protect yourself:
1. Create a dedicated hot wallet (hardware or reputable mobile app) used only for DeFi. Never store long‑term savings there.
2. Transfer only the amount you need for a specific interaction, then move any leftovers back to your cold storage immediately.
3. Regularly review and revoke token allowances with a tool like Revoke.cash; stale approvals are a common attack vector.

Treat your DeFi wallet like a disposable cash envelope — load it, use it, empty it. Share this with someone new to crypto — it could save them!
#Bitcoin #BTC #CryptoSecurity #StaySafe"

Now count words. Let's count manually.

"Every(1) time2 you3 connect4 a5 wallet6 to7 a8 DeFi9 protocol10 you11 expose12 its13 private14 keys15 to16 smart‑contract17 code18 you19 cannot20 fully
🔐 Security tip: the "support agent" who messages you first is not support. Real exchange support doesn't slide into your DMs on Telegram, X or WhatsApp asking you to "verify" your account. 3 red flags that it's a scam 👇 1️⃣ They contact you first and sound urgent ("your account will be frozen in 30 min") 2️⃣ They ask for your 2FA code, seed phrase or a screen share 3️⃣ They send a link that looks almost right (one letter off in the domain) What to do instead ✅ • Open the app yourself and use the official help center • Check any link or contact with Binance Verify before you trust it • Never share codes, keys or seed phrases with anyone. Ever. Your seed phrase is your money. Whoever has it, owns it. Have you ever received one of these messages? 👀 #CryptoSecurity #ScamAlert #Binance #crypto
🔐 Security tip: the "support agent" who messages you first is not support.

Real exchange support doesn't slide into your DMs on Telegram, X or WhatsApp asking you to "verify" your account.

3 red flags that it's a scam 👇
1️⃣ They contact you first and sound urgent ("your account will be frozen in 30 min")
2️⃣ They ask for your 2FA code, seed phrase or a screen share
3️⃣ They send a link that looks almost right (one letter off in the domain)

What to do instead ✅
• Open the app yourself and use the official help center
• Check any link or contact with Binance Verify before you trust it
• Never share codes, keys or seed phrases with anyone. Ever.

Your seed phrase is your money. Whoever has it, owns it.

Have you ever received one of these messages? 👀

#CryptoSecurity #ScamAlert #Binance #crypto
🚨 3 SIGNS OF A CRYPTO OFFER YOU SHOULD WATCH OUT FOR! Have you ever seen a project promising large, guaranteed returns in a short time? Before sending money or connecting your wallet, check the following: ⚠️ 1. Guaranteed profit claims without explaining reasonable risks. ⚠️ 2. Pressure to deposit immediately, claiming the opportunity is about to end. ⚠️ 3. Project identities and information that can’t be verified through independent sources. Don’t trust testimonials or profit screenshots alone. 🔐 Remember: protect your seed phrase, never share your private key, and carefully check website addresses. Have you come across other red flags? Share your experience without revealing personal information. #CryptoSecurity #SCAMalerts #Web3
🚨 3 SIGNS OF A CRYPTO OFFER YOU SHOULD WATCH OUT FOR!

Have you ever seen a project promising large, guaranteed returns in a short time?

Before sending money or connecting your wallet, check the following:

⚠️ 1. Guaranteed profit claims without explaining reasonable risks.

⚠️ 2. Pressure to deposit immediately, claiming the opportunity is about to end.

⚠️ 3. Project identities and information that can’t be verified through independent sources.

Don’t trust testimonials or profit screenshots alone.

🔐 Remember: protect your seed phrase, never share your private key, and carefully check website addresses.

Have you come across other red flags? Share your experience without revealing personal information.

#CryptoSecurity #SCAMalerts #Web3
When a Bitcoin transaction gets stuck and takes a long time to confirm, there’s a feature that can speed it up. At that point, a malicious server may have swapped out the recipient’s address. Here’s how it works in simple terms: the wallet asks an external server what fee to use to speed up the payment. If that server is malicious, it could return not just a fee amount but a completely altered transaction that sends the money somewhere other than where you intended. This isn’t a blockchain hack or a problem with Bitcoin itself. It’s a vulnerability in the way certain wallets communicated with third-party servers for a convenient feature. Developers are already patching the bug. The most important takeaway isn’t technical, but practical: even a foundation like Bitcoin, which everyone considers extremely secure, can have a weak point in some convenient service built around it. The network itself is secure, but the interface you use to access it is also part of your security. I think people update their wallets too rarely, and that’s the main reason these kinds of bugs get the chance to harm anyone. Let me know if you see it differently. $BTC #bitcoin #CryptoSecurity #WalletSecurity
When a Bitcoin transaction gets stuck and takes a long time to confirm, there’s a feature that can speed it up. At that point, a malicious server may have swapped out the recipient’s address.

Here’s how it works in simple terms: the wallet asks an external server what fee to use to speed up the payment. If that server is malicious, it could return not just a fee amount but a completely altered transaction that sends the money somewhere other than where you intended.

This isn’t a blockchain hack or a problem with Bitcoin itself. It’s a vulnerability in the way certain wallets communicated with third-party servers for a convenient feature. Developers are already patching the bug.

The most important takeaway isn’t technical, but practical: even a foundation like Bitcoin, which everyone considers extremely secure, can have a weak point in some convenient service built around it. The network itself is secure, but the interface you use to access it is also part of your security.

I think people update their wallets too rarely, and that’s the main reason these kinds of bugs get the chance to harm anyone. Let me know if you see it differently.

$BTC #bitcoin #CryptoSecurity #WalletSecurity
Headline: Hot Wallet vs. Cold Storage: The Golden Rules of Crypto Self-Custody When entering Web3, how you store your assets is just as important as how you trade them. One of the most critical decisions every crypto participant faces is choosing between hot wallets and cold storage. Understanding the differences between the two is essential for protecting your capital. --- ### 🔥 1. Hot Wallets (Online & Convenient) A hot wallet is connected to the internet. This includes browser extensions, mobile apps, and exchange deposit addresses. • Best for: Daily trading, interaction with decentralized applications (dApps), and fast transfers. • The Advantage: Instant execution and seamless connectivity. • The Risk: Because they remain connected online, they are exposed to phishing links, malicious smart contracts, and device-level malware. --- ### 🧊 2. Cold Storage (Offline & Fortified) Cold storage keeps your private keys completely isolated from the internet, typically on a dedicated hardware device (e.g., a hardware key). • Best for: Long-term savings, treasury reserves, and capital you don't intend to trade daily. • The Advantage: Private keys never touch an internet-connected device, making remote malware or cyberattacks virtually impossible. • The Risk: Physical loss or improper seed phrase backup management. --- ### 💡 The Golden Rule: The 80/20 Custody Model A balanced framework used by experienced participants is to separate your portfolio: 1. Keep 80–90% of your long-term holdings offline in cold storage. 2. Keep only 10–20% (or whatever you are actively trading) in hot wallets for convenience. Never approve smart contract transactions on the same wallet where you keep your primary life savings. How do you split your portfolio custody between hot and cold storage? Share your thoughts below! Disclaimer: For educational purposes only. Never share your recovery seed phrase with anyone. #CryptoSecurity #SelfCustody #Web3 #BinanceSquare #Education #DYOR
Headline: Hot Wallet vs. Cold Storage: The Golden Rules of Crypto Self-Custody

When entering Web3, how you store your assets is just as important as how you trade them. One of the most critical decisions every crypto participant faces is choosing between hot wallets and cold storage.

Understanding the differences between the two is essential for protecting your capital.

---

### 🔥 1. Hot Wallets (Online & Convenient)
A hot wallet is connected to the internet. This includes browser extensions, mobile apps, and exchange deposit addresses.

• Best for: Daily trading, interaction with decentralized applications (dApps), and fast transfers.
• The Advantage: Instant execution and seamless connectivity.
• The Risk: Because they remain connected online, they are exposed to phishing links, malicious smart contracts, and device-level malware.

---

### 🧊 2. Cold Storage (Offline & Fortified)
Cold storage keeps your private keys completely isolated from the internet, typically on a dedicated hardware device (e.g., a hardware key).

• Best for: Long-term savings, treasury reserves, and capital you don't intend to trade daily.
• The Advantage: Private keys never touch an internet-connected device, making remote malware or cyberattacks virtually impossible.
• The Risk: Physical loss or improper seed phrase backup management.

---

### 💡 The Golden Rule: The 80/20 Custody Model

A balanced framework used by experienced participants is to separate your portfolio:
1. Keep 80–90% of your long-term holdings offline in cold storage.
2. Keep only 10–20% (or whatever you are actively trading) in hot wallets for convenience.

Never approve smart contract transactions on the same wallet where you keep your primary life savings.

How do you split your portfolio custody between hot and cold storage? Share your thoughts below!

Disclaimer: For educational purposes only. Never share your recovery seed phrase with anyone.

#CryptoSecurity #SelfCustody #Web3 #BinanceSquare #Education #DYOR
·
--
Bearish
🚨 Ultimate Crypto Security & Scam Alert for Beginners! Staying safe and protecting yourself from scammers should be every crypto trader's top priority. Keep these golden rules in mind to secure your hard-earned funds with $BTC and $BNB {spot}(BNBUSDT) : 📌 Top 5 Safety Rules: • Never Share Private Keys or Seed Phrases: No official admin or support team will ever ask for your seed phrase. Anyone who asks is 100% a scammer! • Enable 2FA (Two-Factor Authentication): Always activate Google Authenticator or a passkey on your Binance account. It is much more secure than SMS verification. • Beware of Fake Links & Phishing: Never connect your wallet or click on unknown links. Always use the official Binance app or website. • Verify Before You Transfer: Always send a small test transaction before transferring funds to a new coin or network. • Ignore "Too Good to Be True" Offers: If someone promises double profits or guaranteed giveaways, recognize it as a trap immediately! 💡 Pro Tip: Security is your own responsibility. One small mistake can wipe out your entire portfolio! 💬 Have you enabled 2FA on your account yet? Let me know in the comments below! 👇 $BTC$BNB #CryptoSecurity #ScamAlert #BinanceSquare #CryptoSafety #ProtectYourFunds
🚨 Ultimate Crypto Security & Scam Alert for Beginners!
Staying safe and protecting yourself from scammers should be every crypto trader's top priority. Keep these golden rules in mind to secure your hard-earned funds with $BTC and $BNB
:
📌 Top 5 Safety Rules: • Never Share Private Keys or Seed Phrases: No official admin or support team will ever ask for your seed phrase. Anyone who asks is 100% a scammer! • Enable 2FA (Two-Factor Authentication): Always activate Google Authenticator or a passkey on your Binance account. It is much more secure than SMS verification. • Beware of Fake Links & Phishing: Never connect your wallet or click on unknown links. Always use the official Binance app or website. • Verify Before You Transfer: Always send a small test transaction before transferring funds to a new coin or network. • Ignore "Too Good to Be True" Offers: If someone promises double profits or guaranteed giveaways, recognize it as a trap immediately!
💡 Pro Tip: Security is your own responsibility. One small mistake can wipe out your entire portfolio!
💬 Have you enabled 2FA on your account yet? Let me know in the comments below! 👇
$BTC $BNB
#CryptoSecurity #ScamAlert #BinanceSquare #CryptoSafety #ProtectYourFunds
$ETH Fixes Critical Glamsterdam Bug Before It Could Put Staking Deposits at Risk 🚨 $ETH developers have patched a vulnerability in the upcoming Glamsterdam upgrade that could have redirected validator deposits to builders. No losses have been reported, and client teams must implement revised rules before the upgrade can progress toward mainnet launch. #Ethereum #ETH #CryptoNews #blockchain #CryptoSecurity {spot}(ETHUSDT)
$ETH Fixes Critical Glamsterdam Bug Before It Could Put Staking Deposits at Risk 🚨

$ETH developers have patched a vulnerability in the upcoming Glamsterdam upgrade that could have redirected validator deposits to builders. No losses have been reported, and client teams must implement revised rules before the upgrade can progress toward mainnet launch.

#Ethereum #ETH #CryptoNews #blockchain #CryptoSecurity
Ethereum Up or Down on October 27?

Ethereum Up or Down on October 27?

99%Up1%Down
Volume $66,914.11
Solana made big news! To stop AI-generated junk reports from flooding the security team, submitting a bug report now requires burning 1 SOL! They received 809 reports in a month, supposedly almost all AI-generated. The development team was at a loss for words and had no choice but to resort to this measure. Airdrop farming won’t be so easy anymore! Solana's making researchers pay 1 SOL per bug report to combat AI spam! After getting flooded with 809 reports in a month, mostly AI-generated, they had to take action. No more free bug hunting! #CryptoSecurity $SOL
Solana made big news! To stop AI-generated junk reports from flooding the security team, submitting a bug report now requires burning 1 SOL! They received 809 reports in a month, supposedly almost all AI-generated. The development team was at a loss for words and had no choice but to resort to this measure. Airdrop farming won’t be so easy anymore!

Solana's making researchers pay 1 SOL per bug report to combat AI spam! After getting flooded with 809 reports in a month, mostly AI-generated, they had to take action. No more free bug hunting!

#CryptoSecurity $SOL
Keystone revealed the scale of the breach: the verification key for hardware wallets was stolen. This means attackers may have been able to counterfeit devices that users believed were authentic. A blow to trust in cold storage for ETH and other assets—at a time when the market is already under pressure. $BTC ETH #DriftHackVictimsBeginClaims #CryptoSecurity $LINK $XRP SOL
Keystone revealed the scale of the breach: the verification key for hardware wallets was stolen. This means attackers may have been able to counterfeit devices that users believed were authentic. A blow to trust in cold storage for ETH and other assets—at a time when the market is already under pressure.

$BTC ETH #DriftHackVictimsBeginClaims #CryptoSecurity $LINK $XRP SOL
🚨 SOL bug bounties now cost 1 SOL per report. AI spam overwhelmed security teams, forcing the permanent burn of 809 submissions in a single month. This move protects network integrity but signals extreme strain on Solana's developer infrastructure. Market Implication: Increased operational costs may dampen short-term developer sentiment, but strengthens long-term network resilience. Will this curb the AI influx or drive vulnerability research underground? #CryptoSecurity $SOL #TradingSignal #CryptoAnalysis
🚨 SOL bug bounties now cost 1 SOL per report. AI spam overwhelmed security teams, forcing the permanent burn of 809 submissions in a single month. This move protects network integrity but signals extreme strain on Solana's developer infrastructure.

Market Implication: Increased operational costs may dampen short-term developer sentiment, but strengthens long-term network resilience.

Will this curb the AI influx or drive vulnerability research underground? #CryptoSecurity

$SOL #TradingSignal #CryptoAnalysis
🚨 LEDGER FACES CLASS-ACTION LAWSUIT AS LEAKED DATA ENDANGERS $BTC HOLDINGS! 💣 Lawyer Ariel Givner just revealed that Ledger is hit with a class-action lawsuit in New York following undisclosed security failures. The complaint alleges a December 2023 breach leaked sensitive customer data, including emails and phone numbers, which quickly surfaced on dark web channels. 🔍 Malicious actors utilized this stolen metadata to launch surgical social engineering attacks, impersonating official representatives to drain self-custody wallets. 🌊 Securing your $BTC off exchanges is only half the battle when personal data vulnerabilities open backdoors for attackers. 🛡️ With phishing tactics becoming far more targeted, what steps are you taking to audit your personal operational security? 🤔 ⚠️ Not financial advice. Always manage your risk. 🛡️ 🏷️ #BTC #CryptoSecurity #HardwareWallet #SelfCustody 🚨 🛡️
🚨 LEDGER FACES CLASS-ACTION LAWSUIT AS LEAKED DATA ENDANGERS $BTC HOLDINGS! 💣

Lawyer Ariel Givner just revealed that Ledger is hit with a class-action lawsuit in New York following undisclosed security failures. The complaint alleges a December 2023 breach leaked sensitive customer data, including emails and phone numbers, which quickly surfaced on dark web channels. 🔍

Malicious actors utilized this stolen metadata to launch surgical social engineering attacks, impersonating official representatives to drain self-custody wallets. 🌊 Securing your $BTC off exchanges is only half the battle when personal data vulnerabilities open backdoors for attackers. 🛡️

With phishing tactics becoming far more targeted, what steps are you taking to audit your personal operational security? 🤔

⚠️ Not financial advice. Always manage your risk. 🛡️

🏷️ #BTC #CryptoSecurity #HardwareWallet #SelfCustody

🚨 🛡️
·
--
Bullish
🔐 The wallet was inactive — but its private key still worked On October 26, 48 wallets linked to Bloom Trading lost 9,408 SOL in just 94 seconds, according to Bitquery's on-chain investigation Five hadn't traded on Bloom since early 2025 Here's the part that matters 👇 $SOL {future}(SOLUSDT) Every drain was signed with the affected wallet's own key — no malicious token approval or smart contract exploit required ⚠️ The source of the key exposure is still unconfirmed But the security lesson is clear Stopping a bot doesn't make a previously shared private key safe again {spot}(SOLUSDT) 📌 If a trading bot has ever held your wallet's private key, moving remaining funds to a fresh wallet with a new key is safer than simply disconnecting the bot An inactive wallet isn't necessarily a secure wallet #solana #CryptoSecurity
🔐 The wallet was inactive — but its private key still worked

On October 26, 48 wallets linked to Bloom Trading lost 9,408 SOL in just 94 seconds, according to Bitquery's on-chain investigation
Five hadn't traded on Bloom since early 2025
Here's the part that matters 👇

$SOL

Every drain was signed with the affected wallet's own key — no malicious token approval or smart contract exploit required

⚠️ The source of the key exposure is still unconfirmed
But the security lesson is clear
Stopping a bot doesn't make a previously shared private key safe again


📌 If a trading bot has ever held your wallet's private key, moving remaining funds to a fresh wallet with a new key is safer than simply disconnecting the bot
An inactive wallet isn't necessarily a secure wallet

#solana #CryptoSecurity
India’s CoinDCX loses another $16 million in USDT from a retired wallet; CEO initially calls it a false alarm An exchange’s “retired wallet” has once again become the target of an attack—this time at CoinDCX, one of India’s veteran platforms. The incident began with an alert that the CEO publicly described as a “false alarm,” but was ultimately confirmed as an actual loss of around $16 million in USDT. It has exposed long-overlooked risk-control vulnerabilities in custody operations. According to Decrypt, the Mumbai-based exchange disclosed that approximately 15.99 million USDT had been transferred out of one of its retired cold wallets. The assets had originally come from last year’s hack, in which around $44 million was stolen. After that incident, they were supposed to be placed in long-term storage and gradually dealt with as “retired” assets. Now, however, funds have been lost again. The timing is noteworthy: the CEO initially called it a “false alarm,” only to later confirm that the loss had actually occurred. This shift from denial to confirmation may be more concerning to the market than the amount lost—it suggests that when the risk first emerged, public disclosure and internal assessment may have been delayed or mistaken. From a market perspective, nearly all of the stolen assets were in USDT, whose price is less correlated with major cryptocurrencies such as BTC and ETH. As a result, the direct impact on overall market liquidity is limited. This makes the incident look more like an isolated risk than a signal of a systemic crisis. However, stablecoins are central to the current market narrative around capital flows. A vulnerability in USDT custody at a major exchange is bound to complicate recent discussions about stablecoin flows and the credibility of reserves. The market reaction may be relatively restrained: since the loss was denominated in USDT and is manageable in scale, its short-term impact on the broader market is likely to be limited, with the main effects being on sentiment and trust. What really matters is whether CoinDCX can fully disclose the movement of the funds, whether it will initiate compensation, and whether its procedures for managing similar retired assets will be reviewed. One counterpoint is that security incidents at a single exchange usually do not spread across the industry. Moreover, the risk of USDT depegging depends primarily on the issuer’s reserves, not on the wallet security of any one exchange. What to watch next: For those following the stablecoin liquidity narrative, the more important question at the trading level is whether incidents like this undermine confidence in USDT’s reserves and custody—not short-term price fluctuations. Watch for how complete the exchange’s subsequent disclosures are, and whether its procedures for managing retired assets are reviewed. #CoinDCX #USDT #CryptoSecurity The above is a summary of information and personal analysis, and does not constitute investment advice. I will continue to monitor the situation and provide updates if there are any significant developments.
India’s CoinDCX loses another $16 million in USDT from a retired wallet; CEO initially calls it a false alarm

An exchange’s “retired wallet” has once again become the target of an attack—this time at CoinDCX, one of India’s veteran platforms. The incident began with an alert that the CEO publicly described as a “false alarm,” but was ultimately confirmed as an actual loss of around $16 million in USDT. It has exposed long-overlooked risk-control vulnerabilities in custody operations.

According to Decrypt, the Mumbai-based exchange disclosed that approximately 15.99 million USDT had been transferred out of one of its retired cold wallets. The assets had originally come from last year’s hack, in which around $44 million was stolen. After that incident, they were supposed to be placed in long-term storage and gradually dealt with as “retired” assets. Now, however, funds have been lost again.

The timing is noteworthy: the CEO initially called it a “false alarm,” only to later confirm that the loss had actually occurred. This shift from denial to confirmation may be more concerning to the market than the amount lost—it suggests that when the risk first emerged, public disclosure and internal assessment may have been delayed or mistaken.

From a market perspective, nearly all of the stolen assets were in USDT, whose price is less correlated with major cryptocurrencies such as BTC and ETH. As a result, the direct impact on overall market liquidity is limited. This makes the incident look more like an isolated risk than a signal of a systemic crisis. However, stablecoins are central to the current market narrative around capital flows. A vulnerability in USDT custody at a major exchange is bound to complicate recent discussions about stablecoin flows and the credibility of reserves.

The market reaction may be relatively restrained: since the loss was denominated in USDT and is manageable in scale, its short-term impact on the broader market is likely to be limited, with the main effects being on sentiment and trust. What really matters is whether CoinDCX can fully disclose the movement of the funds, whether it will initiate compensation, and whether its procedures for managing similar retired assets will be reviewed.

One counterpoint is that security incidents at a single exchange usually do not spread across the industry. Moreover, the risk of USDT depegging depends primarily on the issuer’s reserves, not on the wallet security of any one exchange.

What to watch next: For those following the stablecoin liquidity narrative, the more important question at the trading level is whether incidents like this undermine confidence in USDT’s reserves and custody—not short-term price fluctuations. Watch for how complete the exchange’s subsequent disclosures are, and whether its procedures for managing retired assets are reviewed.

#CoinDCX #USDT #CryptoSecurity

The above is a summary of information and personal analysis, and does not constitute investment advice.
I will continue to monitor the situation and provide updates if there are any significant developments.
September 2026 hack losses: about $768M. 🛡️ Two events drove most of it: Bitget ($387.5M, wallet system breach) and Liquid Network ($318.7M, code flaw that allowed fake coins to be created). The lesson for traders: exchange size is not a security guarantee. Concentrated funds mean concentrated risk. Quick survival checklist: Move idle coins to your own wallet. Split funds across more than one platform. Turn on 2FA and withdrawal whitelists. Keep on exchanges only what you’re actively trading. Backtest before you deploy... #CryptoSecurity #Bitcoin #CryptoTrading
September 2026 hack losses: about $768M. 🛡️

Two events drove most of it: Bitget ($387.5M, wallet system breach) and Liquid Network ($318.7M, code flaw that allowed fake coins to be created).

The lesson for traders: exchange size is not a security guarantee. Concentrated funds mean concentrated risk.

Quick survival checklist:

Move idle coins to your own wallet.
Split funds across more than one platform.
Turn on 2FA and withdrawal whitelists.

Keep on exchanges only what you’re actively trading.

Backtest before you deploy...

#CryptoSecurity #Bitcoin #CryptoTrading
Log in to explore more content
Join global crypto users on Binance Square
⚡️ Get latest and useful information about crypto.
💬 Trusted by the world’s largest crypto exchange.
👍 Discover real insights from verified creators.
Email / Phone number