The function named “Liquidity” that quietly drained investors

In the FastBNB contract's public interface, one function appears under the name Liquidity(uint256). To anyone scanning the contract — even a careful investor reading the function list — that name reads like liquidity management: adding to the pool, topping it up, protecting holders. It sounds like one of the good, defensive functions a project would want.

It does the opposite. Calling it transfers BNB straight out of the contract and into the owner's private wallet. No liquidity is added. It is a plain owner withdrawal — dressed in the name of the very thing it destroys. That mismatch between what the name implies and what the code does is exactly what misleads users into trusting a contract that can be emptied at any moment.

The smoking gun is the decoded on-chain call itself — public, permanent, and reproducible on BscScan:

// Function called on the FastBNB contract (selector 0x198b2eae)
Liquidity(uint256 amount)

  From    : owner wallet   0xf7a4…9b57
  To      : FastBNB        0x8C70…2469
  amount  : 18000000000000000000   // = 18 BNB

  → result: 18 BNB transferred OUT of the contract to the owner

The contract's own design compounds the risk: users' principal deposits can't be withdrawn by users at all — the only path moving that BNB out is the owner's Liquidity() function. Ownership was never renounced.