Peapods Pulls Most Layer-2 Liquidity After Abnormal PEAS Minting Tied to Deployer Key
By Crypto Wire
November 19, 2026
Peapods Finance said abnormal PEAS minting may involve a compromised deployer private key, and that the team has removed about 98% to 99% of its Layer-2 liquidity to limit further extraction. Per coverage of the protocol’s response dated November 18–19, 2026 — including TokenPost and flash wraps citing Foresight News — PEAS was minted on a Layer-2 network, bridged to Ethereum mainnet, and sold. Rug Room desks read that as a key-and-permissions path, not a pool-accounting quirk.
Peapods’ preliminary account says the key in question had been used to set minting permissions and create tokens on the L2. The team states PEAS cannot be minted directly on mainnet; only liquidity already bridged can still be pulled there. Peapods says it has contained PEAS selling pressure, is running a post-incident review, and is attempting to recover funds taken in the incident. Attribute every containment percentage and mint path claim to the project’s stated response via those reports — do not invent a confirmed loss total or a named L2 chain if the primary wrap does not lock one.
For crypto and NFT-adjacent LPs, the operational warning is blunt. Peapods advised users to temporarily remove all on-chain liquidity-provider (LP) and LVF positions while investigation and recovery continue. That is a position-risk notice from the protocol, not a guarantee remaining bridged liquidity is safe. Collectors holding PEAS or LP tokens tied to Peapods rails should treat project channels as the source of truth for any later reimbursement or contract migration — none of those details are confirmed in the first response wave.
Context for the wider exploit tape: this sits beside other mid-November DeFi incidents desks already tracked — including vault and recovery-service stories — but Peapods is a separate mint-permission narrative. Prefer TokenPost / Foresight-cited Peapods statements over aggregators if any figure diverges. Do not invent a Blockaid alert ID, a specific bridge contract address, or a recovered-funds transaction from this wrap.
Risks stay plain. A “may have been compromised” deployer key is a preliminary assessment. Pulling 98–99% of L2 liquidity limits further L2 extraction per the team; it does not by itself prove mainnet sell-pressure is over. Users who leave LP/LVF positions up while the review runs accept residual protocol risk the team itself flagged.
What to watch on-chain next: Track whether remaining bridged PEAS liquidity keeps draining on mainnet and whether Peapods names a recovery wallet cluster or a rotated deployer key in a follow-up — those two prints decide if this stays a contained L2 mint story or becomes a multi-day restitution beat.
Bottom line: Peapods ties abnormal L2 PEAS minting to a possible deployer-key compromise, pulled ~98–99% of L2 liquidity, and told users to temporarily exit on-chain LP and LVF positions while recovery work continues.
Disclaimer: This article is provided for informational and educational purposes only. It does not constitute financial, investment, legal, or trading advice. The NFT market is highly volatile, and past performance is not indicative of future results. Readers should conduct their own research and consult qualified professionals before making any decisions related to digital assets. The cover image for this article may have been created using artificial intelligence (AI).
