According to @PeckShieldAlert, a THORChain user's personal wallet was exploited for an estimated loss of about $1.2 million. Source: @PeckShieldAlert (X, Sep 12, 2025). The alert specifies the affected entity as a user's personal wallet rather than the THORChain protocol. Source: @PeckShieldAlert (X, Sep 12, 2025). No attacker address, exploit vector, or remediation details were provided in the alert text. Source: @PeckShieldAlert (X, Sep 12, 2025). This incident marks a timestamped security event associated with the THORChain ecosystem that traders tracking RUNE may monitor by size (~$1.2M) and timing. Source: @PeckShieldAlert (X, Sep 12, 2025).

According to @PeckShieldAlert, the incident was a compromise of a user's personal wallet and is not related to the THORChain protocol, indicating no confirmed protocol-level exploit on THORChain at this time (source: x.com/PeckShieldAlert/status/1966409664008233379). For trading, this clarification means the event should be treated as user-side security risk rather than a protocol failure when assessing RUNE exposure and THORChain liquidity risk (source: x.com/PeckShieldAlert/status/1966409664008233379; reference: x.com/PeckShieldAlert/status/1966399712741016051).

According to @PeckShieldAlert, THORChain suffered an exploit with an estimated loss of about $1.2 million. Source: @PeckShieldAlert on X, Sep 12, 2025. The alert did not provide details on the attack vector, affected chains, or mitigation steps, indicating limited public information at this time. Source: @PeckShieldAlert on X, Sep 12, 2025. For trading, the reported exploit creates immediate headline risk for RUNE and THORChain liquidity pools; traders can monitor centralized exchange order books, funding rates, and on-chain swaps for stress potentially linked to the incident. Source: @PeckShieldAlert on X, Sep 12, 2025. Market participants should track official THORChain updates for confirmations, patches, and any service changes that could impact cross-chain routing and LP withdrawals. Source: @PeckShieldAlert on X, Sep 12, 2025.

According to @PeckShieldAlert, @zachxbt reports SwissBorg suffered an exploit on Solana with 192.6K SOL valued at about $41.5M stolen (source: @PeckShieldAlert). According to @PeckShieldAlert, the attacker deposited 100 SOL to Bitget, indicating exchange touchpoint activity relevant for tracing flows (source: @PeckShieldAlert).

According to @PeckShieldAlert, Nemo Protocol on Sui Network was exploited for $2.4 million on Sep 8, 2025, with funds denominated in USDC, source: @PeckShieldAlert. According to @PeckShieldAlert, the attacker bridged USDC via Circle from Arbitrum to Ethereum following the incident, establishing a clear cross-chain path, source: @PeckShieldAlert. According to @PeckShieldAlert, the affected ecosystems and assets explicitly identified are Sui, Arbitrum, Ethereum, and USDC, which defines the networks and token involved in the outflow, source: @PeckShieldAlert.

According to @PeckShieldAlert, Venus Protocol has proposed an emergency governance vote to force-liquidate the attacker's position following a phishing attack, with voting requested within the next hour and the official vote link shared by @PeckShieldAlert.

According to @PeckShieldAlert, the loss for the phished Venus Protocol user has been corrected to approximately 13.5 million dollars after initial estimates were overstated by not excluding the debt position, and the update specifies this was a user-level phishing incident rather than a protocol exploit (source: @PeckShieldAlert, Sep 2, 2025).

According to @PeckShieldAlert, a Venus Protocol user lost about $27 million after approving a malicious transaction that granted token spending rights to attacker address 0x7fd8...202a, enabling asset transfers; source: @PeckShieldAlert. Given the user-targeted phishing vector and token-approval mechanism described, traders with exposure to Venus-related markets can prioritize allowance checks and monitor addresses interacting with 0x7fd8...202a for abnormal flows to gauge short-term risk; source: @PeckShieldAlert.

According to @PeckShieldAlert, Ethereum’s Layer-2 network StarkNet has been down for over 4 hours due to a service outage, source: @PeckShieldAlert. Traders should assume elevated execution and settlement risk on StarkNet during the reported downtime and verify network status before routing transactions or managing StarkNet-dependent positions, source: @PeckShieldAlert.

According to @PeckShieldAlert, DeFi protocol @bunni_xyz has suffered an exploit with an estimated loss of about $2.4 million, signaling an active security incident tied to Bunni contracts (source: @PeckShieldAlert on X, Sep 2, 2025). The alert confirms a material loss event that elevates smart contract and counterparty risk for users interacting with Bunni-related liquidity or positions until an official fix or postmortem is released (source: @PeckShieldAlert on X). Traders should verify any direct exposure to Bunni-linked contracts and await remediation updates from the project’s official channels before initiating new interactions (source: @PeckShieldAlert on X).

According to @PeckShieldAlert, approximately 16 major crypto exploits were recorded in August 2025 with total losses of 163 million dollars, marking a 15 percent increase from July's 142 million dollars, source: PeckShieldAlert on X, September 1, 2025. According to @PeckShieldAlert, BTCturk experienced its second major breach in just over a year with losses exceeding 50 million dollars, following a 54 million dollar hack in June 2024, source: PeckShieldAlert on X, September 1, 2025. According to @PeckShieldAlert, the month-over-month rise in exploit-driven losses highlights elevated operational and custodial risk across centralized and decentralized venues that traders track when assessing venue and counterparty exposure, source: PeckShieldAlert on X, September 1, 2025.

According to @PeckShieldAlert, Binance Futures experienced a temporary service interruption on Aug 29, 2025, lasting about 20 minutes; during the outage, contract transfers were suspended and have now been restored, source: @PeckShieldAlert. No further impact details were disclosed, source: @PeckShieldAlert.

According to PeckShieldAlert, address 0xac1f...f553 was liquidated for 29.68 WBTC, valued at approximately $3.41 million, as BTC fell below $113,000 (source: PeckShieldAlert). According to PeckShieldAlert, the same address still supplies 42.71 WBTC against roughly $3.1 million in stablecoin borrows, highlighting ongoing on-chain leveraged exposure (source: PeckShieldAlert).

According to @PeckShieldAlert, address 0x1526...F32f was hit by a phishing attack with an estimated loss of about $1,000,000 across cryptocurrencies and NFTs, with stolen assets identified as 623,600 SPX worth about $804,000, 71,600 CULT worth about $88.87, and 371.417 harrypotterobamasonic10in worth about $31, reported on X on Aug 22, 2025, source: @PeckShieldAlert. According to @PeckShieldAlert, the alert explicitly lists $SPX and $CULT among the taken tokens, highlighting token-specific exposure for traders tracking on-chain security incidents, source: @PeckShieldAlert.

According to @PeckShieldAlert, the official Puffer Finance website (puffer.fi) and its social media channels have been compromised, and users are instructed not to interact with any Puffer applications or access the official social channels (source: @PeckShieldAlert). According to @PeckShieldAlert, traders should immediately halt any activity that involves connecting wallets or signing transactions via puffer.fi or links from Puffer’s official social accounts to mitigate compromise risk (source: @PeckShieldAlert). According to @PeckShieldAlert, market participants should treat all Puffer-related frontends and links as unsafe and await further security updates from verified sources before resuming activity (source: @PeckShieldAlert).

According to @PeckShieldAlert, crypto exchange BtcTurk has been hacked with estimated losses of approximately $49 million; source: @PeckShieldAlert. @PeckShieldAlert reports the breach and quantifies the loss, indicating a major security incident at the exchange; source: @PeckShieldAlert.

According to @PeckShieldAlert, as the market corrected and BTC fell below $120K, a whale long position on BTC via Venus was liquidated for 779.41 vBTC valued at USD 1.55M. @PeckShieldAlert specifies that the liquidation occurred on Venus and provides the size and timing on Aug 14, 2025, offering a concrete datapoint on BTC-linked DeFi liquidation activity.

According to @PeckShieldAlert, 58.2 BTC (about $7 million) were drained from the Odin GodOfRunes platform, source: @PeckShieldAlert. The attackers added liquidity using SATOSHI, artificially inflated the token price, and then removed liquidity to receive BTC returns, source: @PeckShieldAlert. Attacker addresses were disclosed in the alert, source: @PeckShieldAlert.

According to @PeckShieldAlert, a Radiant Capital exploiter-labeled address swapped 3,091 ETH for 13.26M DAI and transferred the stolen funds to a new address 0xA4F2...eB51 (source: @PeckShieldAlert). According to @PeckShieldAlert, Radiant Capital previously suffered a $53M hack on Oct 17, 2024, and this conversion represents roughly 25% of that reported amount (source: @PeckShieldAlert). Based on @PeckShieldAlert data, the swap size implies an average execution near $4,290 per ETH, offering traders a reference point for on-chain liquidity and slippage in ETH/DAI pairs (source: @PeckShieldAlert). According to @PeckShieldAlert, the new address 0xA4F2...eB51 is the current destination to monitor for subsequent on-chain movements (source: @PeckShieldAlert).

According to @PeckShieldAlert, the ResupplyFi exploiter laundered 2,280 ETH (roughly $9.8M) through Tornado Cash on August 12, 2025, confirming active movement of incident-related funds, source: @PeckShieldAlert. The alert does not report any exchange deposits, freezes, or recovery actions, indicating no containment was stated by the source at the time of the alert, source: @PeckShieldAlert. Traders can monitor the addresses and follow-up alerts referenced by the source to track further fund movements relevant to ETH market flows, source: @PeckShieldAlert.