KAVA PROBES POTENTIAL SECURITY ISSUE AS TOKEN CRASHES OVER 40%! @KAVA_CHAIN is investigating unexpected behavior from a dApp in its ecosystem after on-chain activity involving…
Crypto Banter Published: 2026-11-14 13:56 UTC Collected: 2026-11-14 15:56 UTC Original language: Not supplied by source
🚨KAVA PROBES POTENTIAL SECURITY ISSUE AS TOKEN CRASHES OVER 40%!
@KAVA_CHAIN is investigating unexpected behavior from a dApp in its ecosystem after on-chain activity involving the bridging and sale…
🚨KAVA PROBES POTENTIAL SECURITY ISSUE AS TOKEN CRASHES OVER 40%!
@KAVA_CHAIN is investigating unexpected behavior from a dApp in its ecosystem after on-chain activity involving the bridging and sale of kava:native tokens on BNB Smart Chain.
The project stated the event is not an infinite mint and is isolated and contained within Kava Lend.
Partner exchanges paused related deposits and withdrawals as a precaution while the token fell more than 40% amid the uncertainty, with further details expected shortly.
Collected source wording; claims are attributed to the source and are not independently verified here.
AI context is not available for this statement. The original source can be read independently.
This is a collected public statement, not a new announcement by Atlas Pulse AI. Read the original source for full wording and publication context.
🚨HOW THE LIGHTER FUNDS MOVED! According to @bubblemaps tracking: 1. Wallet 0xb3f, funded with a small amount via Across, pulled roughly $10.39M in USDC from @Lighter_xyz. 2. The funds were converted to $ETH. From the main wallet, about $2.32M was sent out in smaller pieces. 3. T
🚨LIGHTER ATTACKER MOVING FUNDS TO BUY MONERO! On-chain activity shows the wallet linked to the @Lighter incident is moving funds into Hyperliquid to purchase $XMR. Monero is a privacy-focused coin that is significantly harder to trace than most other assets.
🚨UPDATE: LIGHTER INCIDENT APPARENTLY TIED TO LEAKED API KEYS, NOT PROTOCOL EXPLOIT! Early analysis indicates the activity was not a protocol-level hack. An attacker used leaked API keys from two large market maker accounts to close positions, create a 0% fee public pool controll