MemeCore M Token Collapse Without Confirmed Trigger
MemeCore’s M token fell from near $2.92 to as low as $0.51 within 24 hours, erasing close to $3 billion in market value on roughly $21 million in volume, with no confirmed exploit, hack, or public catalyst identified.
On 2026-06-25, MemeCore’s M token experienced a rapid market collapse, declining about 74% over 24 hours from near $2.92 to as low as $0.51 before steadying around $0.74.<sup class="cite">[1]</sup> CoinDesk reported that the move erased close to $3 billion in market value and reduced capitalization to about $969 million from roughly $3.8 billion, despite only about $21 million in daily trading volume.<sup class="cite">[2]</sup><sup class="cite">[3]</sup><sup class="cite">[4]</sup> No confirmed exploit, hack, or announcement has been identified in the present record as the trigger for the sell-off.<sup class="cite">[5]</sup> The principal mechanism therefore remains contested: the dossier does not establish whether the event was a rug pull, insider distribution, or another form of market dislocation. Earlier public allegations by ZachXBT concerning insider manipulation and suspicious withdrawals provide context but do not resolve attribution.<sup class="cite">[6]</sup><sup class="cite">[7]</sup>
This record was prepared from the structured brief, which relied on contemporaneous reporting by CoinDesk and incorporated attributed public allegations cited in that report. Verification was limited to claims expressly documented in the source record: price movement, market-cap change, trading volume, the absence of a confirmed catalyst, and the existence of prior allegations regarding insider behavior and withdrawals. No court filings, exchange incident reports, contract-level forensic analyses, or independently verified on-chain transaction datasets were provided in the dossier. Accordingly, causal interpretation has been restricted to what the source explicitly stated, and unresolved attribution has been preserved as unresolved.
The event consisted of a sharp collapse in the market price of MemeCore’s M token on 2026-06-25. CoinDesk reported that the token fell about 74% over 24 hours, moving from near $2.92 to as low as $0.51 before steadying around $0.74.[1] In the same reporting, the decline was said to have erased close to $3 billion in market value, with M’s capitalization dropping to about $969 million from roughly $3.8 billion.[2][3] The dossier classifies the event as a rug pull for archive purposes, but the source record itself did not establish a definitive trigger or mechanism.[5]
The earliest pivotal context in the present record predated the collapse. CoinDesk cited public allegations made by ZachXBT in April 2026, in which he questioned why Kraken had listed M for spot trading on 2025-07-03 and alleged that insiders had manipulated the token’s price to a $6 billion market capitalization and an $18 billion fully diluted valuation.[6] CoinDesk also quoted ZachXBT as stating that there were about $7.9 million in suspicious Kraken withdrawals to 18 newly created wallets, with 11.7 $M sitting total and valued at $39.8M at the time of his post.[7] These allegations were part of the public record before the June collapse, but the dossier did not provide independent forensic confirmation of them, nor did it connect them through verified transaction evidence to the subsequent sell-off.[6][7]
The collapse itself appears, from the source record, to have occurred without a documented external catalyst. CoinDesk reported no confirmed news, exploit, hack, or announcement to explain the move.[5] That absence is analytically important because it narrows the set of mechanisms that can be established from the available evidence. In incidents where a smart-contract exploit, bridge compromise, or custody breach has been documented, the causal chain is typically anchored by transaction traces, protocol disclosures, or exchange statements. Here, by contrast, the record remained limited to market behavior and prior allegations. As of 2026-06-25, it has not been established in the dossier that the decline resulted from a protocol failure, an exchange failure, or a publicly disclosed treasury action.[5]
CoinDesk further reported that the move took place on roughly $21 million in daily trading volume.[4] Relative to the reported change in capitalization, the source characterized trading as thin.[4] In practical terms, thin volume during a large repricing is consistent with a market structure in which limited liquidity can permit outsized price movement, particularly where supply is concentrated or where confidence is fragile. The dossier’s lesson tags reflect those structural concerns, including founder concentration, single point of control, commingled funds, and absence of withdrawal monitoring, but those tags should be read as analytical classification rather than as independently proven facts about the internal operations of MemeCore in this specific incident. The source record directly supports only that prior allegations had raised questions about insider manipulation and suspicious withdrawals, and that the crash itself lacked a confirmed public trigger.[5][6][7]
The sequence therefore remained incomplete at the close of the present record. A plausible chronology, limited to what is documented, began with the token’s spot listing on Kraken on 2025-07-03, followed by public scrutiny in April 2026 over alleged insider price support and suspicious withdrawals, and culminated in the 2026-06-25 price collapse.[6][7] What the dossier did not provide were the evidentiary links that would convert that chronology into a verified mechanism: no transaction hashes, no contract addresses, no treasury wallet movements, no exchange surveillance findings, and no issuer explanation were included. For that reason, the event can be described with confidence as a severe market collapse, but not yet as a conclusively demonstrated insider dump or operational rug pull.[5]
The documented consequences were material but narrowly defined. CoinDesk reported a decline from roughly $3.8 billion in market capitalization to about $969 million, representing close to $3 billion in value erased during the move.[2][3] The token price remained well below its reported pre-collapse level even after steadying around $0.74.[1] No legal or regulatory action was described in the dossier, no recovery process was documented, and no user-loss accounting, reimbursement plan, or formal incident report was provided as of 2026-06-25.[5]
Discussion
Within the CryptoMortem archive, this incident ranked #7 of 56 by severity, placing it in the 89.3th percentile, and it ranked #1 of 4 within the same event type.<sup class="cite">[2]</sup> On the archive’s own classification, it therefore sat among the largest documented market-collapse events and was the largest rugpull-classified case in that subset. The archive context also matters: 57 total events have been catalogued, with 27 in the 12 months preceding this incident, indicating that the event occurred in a period of elevated case frequency. The pattern profile aligned with recurrent structural weaknesses already present elsewhere in the archive. Commingled funds had been observed in 6 prior events, including 3 in the past 12 months. Founder concentration had appeared in 8 prior events, including 1 in the past 12 months. Single point of control was the most recurrent pattern, observed in 30 prior events, including 14 in the past 12 months. Absence of withdrawal monitoring had been observed in 14 prior events, including 9 in the past 12 months. Those counts do not prove that each pattern was operationally present here, but they show that the dossier’s classification mapped onto familiar failure modes rather than an isolated anomaly. Comparative recovery data were limited but unfavorable. For event type rugpull, the archive contained 1 other record with mean recovery 0.0% and mean resolution 508 days. For the attack vector labelled rugpull, there were 3 prior events in the archive, with cumulative $0.00B affected, 0 fully recovered, and 0 with low/no recovery. Because this case lacked a confirmed exploit or formal resolution path, it more closely resembled unresolved market-structure failures than technically attributable hacks. Its distinguishing feature was scale: a collapse of close to $3 billion without a confirmed trigger placed it at the upper end of loss severity while leaving mechanism and accountability unusually underdetermined.
Comparative analytics
All comparisons computed against the 57-event CryptoMortem archive at time of publication.
- Severity rank across full archive: #7 of 56 (89.3th percentile).
- Severity rank within same event type: #1 of 4.
- Attack vector "Rugpull": 3 prior events in archive, cumulative $4M; 0 fully recovered, 0 with low or no recovery.
- Event type "Rugpull": 1 other records in archive, mean recovery 0.0%, mean resolution 508 days.
- Pattern "Commingled Funds": observed in 6 prior events (3 in the past 12 months).
- Pattern "Founder Concentration": observed in 8 prior events (1 in the past 12 months).
- Pattern "Single Point Of Control": observed in 30 prior events (14 in the past 12 months).
- Pattern "Absence Of Withdrawal Monitoring": observed in 14 prior events (9 in the past 12 months).
- Archive context: 57 events catalogued; 27 in the 12 months preceding this incident.
Limitations
The present record does not establish what caused the sell-off. The dossier explicitly leaves unresolved whether the event was a rug pull, an insider dump, or another mechanism, and it provides no on-chain transaction hashes, contract addresses, or verified attacker attribution. No court filings, regulatory notices, exchange surveillance findings, or issuer incident reports were included. Public allegations cited through CoinDesk provide context, but they do not by themselves prove causation or responsibility. No legal or regulatory action is described in the dossier, and no recovery status, reimbursement process, or formal remediation plan has been documented as of 2026-06-25.
Timeline
- Kraken lists M for spot trading
CoinDesk cited ZachXBT asking why Kraken listed M on July 3, 2025 and how it passed due diligence.
source → - ZachXBT posts allegations about insider manipulation
CoinDesk said ZachXBT alleged insiders had manipulated M’s price and concentrated supply.
source → - M token begins sharp collapse
CoinDesk reported M fell from near $2.92 to as low as $0.51 within 24 hours.
source → - CoinDesk publishes crash report
CoinDesk published the report describing the drop, thin volume, and lack of a confirmed catalyst.
source →
Who was involved
- Krakenexchangebystander
- ZachXBTpersonbystander
- M tokenprojectvictim$3.00B
- MemeCoreprojectvictim$3.00B
Structural failures identified
Sources
- MemeCore's M token suddenly crashes 80% with no clear trigger, CoinDesk — Price collapse, market-cap loss, thin volume, lack of confirmed catalyst, and ZachXBT allegations