Slice Protocol Exploit on Base Drains $41K as FundsModule Trusts Fake Payout Contracts

Slice Protocol Exploit on Base Drains $41K as FundsModule Trusts Fake Payout Contracts


A FundsModule contract linked to Slice, an onchain commerce protocol running on Base, lost about $41,000 in Ether (ETH) and USD Coin (USDC) after an attacker exploited a flaw in how the contract checked incoming funds. The contract paid out from its pooled reserves based on amounts reported by contracts the attacker had deployed, even though those contracts sent no assets.

Blockchain security firm TenArmor flagged the attack on October 21, 2026, and identified the exploit transaction on Basescan. Fellow security firm SlowMist later published a technical breakdown of the exploit and placed the net loss at about $41,000, in line with TenArmor’s estimate.

Base is an Ethereum layer-2 (L2) network incubated by Coinbase. Slice describes itself as an onchain commerce protocol. It lets sellers run decentralized stores called slicers, with each store’s ownership represented by ERC-1155 tokens that split payments among holders. ERC-1155 is an Ethereum token standard that lets a single contract manage multiple token types.

How the Slice FundsModule Exploit Worked

The FundsModule holds pooled ETH and USDC reserves on Slice’s Base deployment. According to SlowMist, the flaw sat in the function with the selector 0x9d2edfac. A function selector is the first four bytes of a hash of a function’s signature, which a contract uses to route each call to the correct code.

SlowMist said the function trusted the release amounts returned by source contracts that the caller chose. It did not confirm that the matching ETH or USDC had actually reached the protocol.

The attacker supplied two self-deployed source contracts. Each reported a nonzero release amount while transferring zero assets. With the relevant flag in the call set to true, the FundsModule used those unbacked figures to calculate and execute immediate withdrawals from its pooled reserves directly to the attacker.

Onchain investigator Sprunky added that the attacker deployed a helper contract about one minute before the exploit. That contract released 62 slicers into the FundsModule before calling the vulnerable function with the two fake source contracts.

The transaction record shows ETH and USDC moving from several BeaconProxy contracts into the FundsModule proxy, followed by a large outflow to the attacker’s address. A proxy is a contract that forwards calls to a separate implementation contract holding the logic, which allows developers to upgrade code without changing the address users interact with.

Key Addresses Linked to the Attack

A Familiar Accounting Flaw

The Slice incident is a case of missing external state verification. The contract accepted a self-reported figure instead of measuring the ETH or token balance it actually received.

Similar accounting logic has failed elsewhere this month. On October 3, SlowMist reported that an attacker exploited MALT’s swap function, which treated treasury-funded DAI as caller-supplied funds and led to a loss of about $72,000. On October 9, SlowMist also flagged the BitBay and EtherVista exploits, which together drained about $32,600 through withdrawal and invariant flaws on Polygon and Ethereum.

Latest in a String of Base Exploits

The Slice exploit adds to a run of incidents involving projects on Base this month. On October 2, GoldPesa’s GPXHooks contract was allegedly drained for about $114,000 through a flaw in its liquidity rebalancing process.

Two days later, an unidentified vault on Base lost about 1,783 wrapped staked Ether (wstETH), worth roughly $6 million, after a newly deployed contract gained whitelist access. On October 12, Autheo’s THEO token lost about $1.7 million in a Hyperlane bridge exploit on Base. Base was also among the four networks hit when losses from the UNCX Vesting V2 exploit reached about $1.49 million.

Across the industry, DefiLlama’s hacks database recorded $2.245 billion in losses across 299 incidents in 2026 as of October 19.

Slice had not issued a public statement on the incident at the time of writing. Investigators continue to monitor the wallets linked to the exploit for further fund movements.

Also Read: Drift Protocol Exploiter Moves $61.5M in ETH to Tornado Cash After 2 Months


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *