Security Incident: Developer Wllet CompromisedSecurity Incident: Developer Wallet Compromised

Family, I need to speak to you plainly today.

On Monday, 12 October 2026, our developer wallet was hacked, and the attacker used it to take ownership of the $ZUBA smart contract. I am sharing everything openly because you deserve the full truth from us first, not from rumours.

This is a challenging time, but it calls for no panic. We are working on it every hour, and we will make sure everyone recovers from this.

What happened, step by step

Everything below is public on BNB Smart Chain and can be checked on BscScan. Our contract address is 0xE1bf97baCF682AE17cA3E239aB68a7b525f994A4.

1. The attacker took control of the contract

At 02:44:47 AM UTC on 12 October 2026 (block 127133369), the attacker used our compromised developer wallet 0x5ee9926564cB98ab3EBc256bCadDD1372cb7f53f to call Transfer Ownership on the $ZUBA contract, moving ownership to a wallet they control. The transaction went through.

Transaction hash: 0x4e971e7bffd0881234e4ff114456aa9ab693e1806d33545a4650b31b9dcedec8

2. We fought to take it back

As soon as we noticed, I tried several times to take ownership back and to renounce it, so the attacker could not use it. You can see those attempts in the transaction list as Transfer Ownership and Renounce Ownership calls marked with a red sign. They failed, because the contract only accepts these commands from its current owner, and after the hack that owner was no longer us.

3. The hacker set buy and sell tax to 100%

With ownership in hand, the hacker's wallet 0xeD86643D…aD4c9442F called Set Buy Tax and Set Sell Tax and raised both to 100%. In simple words, this means any buy or sell right now gives the trader nothing back. The hacker did this to freeze the market so nobody can trade out.

The contract owner also controls other settings such as blacklisting and whitelisting wallets, which is why this ownership change is so serious.

4. Their real target: our LP lock next month

Our liquidity (the LP that makes trading possible on PancakeSwap) is locked on PinkSale (PinkLock V2) and the lock ends next month. The hacker's goal is clear: freeze trading now with the 100% taxes, wait for the lock to end, and then try to take the liquidity.

We know their plan, and we are acting before that date.

What you should do right now

• Do not buy or sell $ZUBA until we post our next update. With 100% tax on both sides, any trade will be lost.
• Hold your tokens and keep your wallet safe. Your $ZUBA balance is still recorded on-chain, and that record matters for the recovery.
• Nobody from ZUBA will ever DM you first or ask for your seed phrase, private key or a "recovery fee". Anyone offering to "recover" your tokens is a scammer. Ignore and report them.
• Only trust updates from these places: the Dev Notes on zubatoken.com, our X @zubatoken, and our Telegram t.me/zubatokenchat.

What we are doing

• Securing the team. We have secured our remaining wallets and are checking every key and device connected to the project.
• Tracing the hacker. We are following every wallet and transaction linked to this attack on-chain. The blockchain keeps a permanent record, and we are tracing it step by step.
• Reporting the addresses. We are reaching out to security partners, PinkSale and the platforms involved to flag the hacker's wallets.
• Planning the recovery. We are looking at redeploying the $ZUBA contract so the community can move to a safe, clean token that the hacker has no control over. We will announce the decision and the full plan once it is finalised.

Our promise

ZUBA is bigger than one hacked wallet. The games, the animation, the story, our partners and this community are all still here, and so am I.

We will make sure everyone recovers from this attack. Our next line of action will be shared here, and we will carry it out so that every holder feels as little of the impact as possible.

Stay calm, stay together and stay alert. We will come back stronger.

Dev. Vicky Founder, ZUBA Token