Data 2026-05-13

$OPTIMUS factory: 17 fake Tesla robot tokens shipped in 9 hours

Seventeen $OPTIMUS-branded contracts landed on Ethereum on May 11 between 20:44 and 06:03 UTC. Top score 100/100, multiple confirmed honeypots with buy_failed + sell_failed + hidden_owner. Full anatomy.

Between 2026-05-11 20:44 and 2026-05-12 06:03 UTC, seventeen separate ERC-20 contracts using the name Optimus Prime and ticker OPTIMUS shipped on Ethereum mainnet. Two scored a perfect 100/100 on RektRadar with all honeypot flags firing simultaneously. The first batch of three landed within twenty minutes of each other - a textbook brand-jack burst riding the Tesla humanoid robot meme.

Screenshot of the RektRadar result page for one of the OPTIMUS honeypot contracts at 0xc4e6fb94aa44541c3cfda29f510d825550b4417d. Token name Optimus Prime, symbol OPTIMUS, deployed 11 May. Risk score 100 out of 100 in a red RISK badge with the note Multiple risk indicators detected. Visible flags include Buy Failed, Sell Failed, Honeypot, Hidden Owner, Conditional Transfer, Trading Control, Approve With Transfer, Block Dependent Logic, Reflection Token. Below the flags a deployer-network 3D mini graph shows the contract connected to its deployer wallet and a small green cluster of sibling EOAs.

This is the fifth large-scale brand-jack we have walked through publicly, after MOODANG, Unicat, $CLAUDE, and KEKIUS. Same mechanics, different ticker.

The scoreboard - 17 OPTIMUS contracts, all detected

AddressScoreFlagsVerifiedDeployed (UTC)
0xc4e6fb…417d10016Yes2026-05-11 21:14
0x9a49be…582f10016Yes2026-05-11 21:33
0xe73f2d…5c0e8914No2026-05-11 21:33
0x9df737…e8c48616Yes2026-05-11 23:14
0xbcb2bc…62bd8016Yes2026-05-11 22:03
0x3b0e37…8b4f7012No2026-05-11 21:03
0xc5df31…86d3706No2026-05-11 20:44
0xbdd991…bb2d7011-2026-05-11 21:13
0x3e73a3…aaaa7010No2026-05-11 21:12
0x99dc2a…6be67012No2026-05-11 21:34
… plus 7 lower-score variants (60 / 50 / 40 / 29) deployed in the same window

Seventeen distinct contract addresses. Same name. Same symbol. Same 9-hour window. No legitimate token launch deploys seventeen times under one identity - this is a coordinated factory.

Anatomy of the worst one - 0xc4e6fb...417d

The top-scoring contract earns its 100/100 by carrying every honeypot indicator in our catalog:

  • buy_failed - buy simulation reverts on a fresh wallet. The exchange cannot accept new buyers.
  • sell_failed - sell simulation reverts. Existing holders cannot exit.
  • honeypot - the meta-flag confirming items 1 and 2 are not transient (multiple test amounts, multiple routers).
  • hidden_owner - ownership address not exposed via owner(). The deployer hid it behind a proxy slot.
  • conditional_transfer - internal _transfer routes through a block-number gate the deployer controls.
  • trading_control - explicit enableTrading() / setTrading() function with onlyOwner modifier.
  • approve_with_transfer - approve() silently triggers a transfer. Approving the router drains the wallet.
  • block_dependent_logic - reads block.number / block.timestamp in the trade path. Anti-bot at launch, anti-everyone forever.
  • reflection_token - implements _rTotal / _rOwned accounting, often used to fake a tax distribution that accumulates to the deployer.
  • liquidity_at_creation - LP added in the same transaction as the contract deployment. Programmatic, not organic.
  • creator_holds_all_lp - the deployer holds 100% of the LP tokens. One transaction to pull it all.
  • new_wallet - the deployer wallet was funded < 7 days before this contract.
  • buy_only_pattern - historical swap activity shows buyers but no successful sellers - the classic honeypot tell.
  • multi_flag_rug_setup - combined signal triggered when 3+ flags from the “new_wallet / creator_holds_all_lp / unverified / no_dex_pair / mass_deployer” set fire together.
  • low_liquidity - initial pool was thin enough that even the modeled buy was within slippage limits.
  • no_graph_data - funder relationship hasn’t yet been mapped by the network analyzer at scan time.

Sixteen flags. The contract is verified on Etherscan (which adds marketing trust), and reading the verified source confirms every signal above.

Why Optimus attracts scammers

Three reasons converge:

  1. Tesla’s flagship humanoid push. Optimus is the public face of Tesla’s robotics ambition. Musk has personally tweeted about Optimus updates at least 30 times in the past year. The audience for “Tesla robot crypto” exists and is searchable.
  2. No official Optimus / Tesla token. Tesla has zero on-chain footprint. Anybody searching “Optimus token” or “Tesla robot crypto” finds whatever SEO ranks first, and SEO can be bought with shilling and fake liquidity.
  3. The “Prime” suffix is plausible. “Optimus Prime” sounds plausibly like a strategic naming - Tesla often uses cinematic / sci-fi-adjacent branding. Buyers who would dismiss a generic dog-coin will buy a Tesla-Optimus-themed token without realizing both are the same trap.

This is the same pattern documented in the $CLAUDE rug pull factory and the AI brandjack post on $xAI and $SAM. The bait is the brand. The contract is just the delivery mechanism.

The 9-hour timeline

2026-05-11 20:44 ← 0xc5df31... (70/100, 6 flags) - first hit, no LP yet
2026-05-11 21:02 ← 0x69c1ca... (50/100, 4 flags)
2026-05-11 21:03 ← 0x3b0e37... (70/100, 12 flags)
2026-05-11 21:12 ← 0x3e73a3... (70/100, 10 flags)
2026-05-11 21:13 ← 0xbdd991... (70/100, 11 flags)
2026-05-11 21:13 ← 0x1a6aa1... (40/100, 4 flags)
2026-05-11 21:14 ← 0xc4e6fb... (100/100, 16 flags) - first FULL honeypot
2026-05-11 21:33 ← 0x9a49be... (100/100, 16 flags) - second FULL honeypot
2026-05-11 21:33 ← 0xe73f2d... (89/100, 14 flags)
2026-05-11 21:34 ← 0x99dc2a... (70/100, 12 flags)
2026-05-11 21:42 ← 0x7d3669... (29/100, 2 flags)
2026-05-11 21:52 ← 0x37389e... (60/100, 5 flags)
2026-05-11 22:03 ← 0xbcb2bc... (80/100, 16 flags)
2026-05-11 22:33 ← 0x1030ad... (40/100, 3 flags)
2026-05-11 23:14 ← 0x9df737... (86/100, 16 flags)
2026-05-12 06:03 ← 0x6301ba... (29/100, 2 flags) - trailing one, 7 hours later

Three things to notice:

  1. All seventeen contracts fall within nine hours of the first deployment. No legitimate community launches a token seventeen times in one night.
  2. The honeypots cluster around 21:14-23:14 - that’s the window where the deployers shipped their fully-loaded variants. The lower-scored contracts on either side are likely scaffolds, tests, or quick-throws that did not get the full honeypot payload.
  3. One trailing contract on 05-12 at 06:03 suggests at least one deployer wallet is still iterating - the operation may not yet be done.

What victims see

The high-score variants (0xc4e6fb, 0x9a49be, 0x9df737, 0xbcb2bc) all share the same victim UX:

  1. Buyer finds the contract via Twitter shill, Telegram group, or organic Google search on “Optimus token Tesla crypto”.
  2. Buyer spends ETH on Uniswap. Buy transaction fails on the worst variants (buy_failed), or succeeds on the slightly cleaner ones.
  3. On the variants where the buy succeeds, the wallet now shows an OPTIMUS balance.
  4. Buyer waits. Tries to take partial profit.
  5. Sell transaction reverts with “transfer failed” or “insufficient gas” (often the wallet rephrases the revert misleadingly).
  6. Deployer pulls the LP. The 100% creator-held LP tokens make this a single-transaction drain.

For the worst-scored contracts, even step 3 doesn’t work - the contract is essentially a deposit-only sink. Buyers send ETH, get nothing routable back, and have no chain of evidence to chase.

Three rules that catch every variant

You do not need RektRadar to avoid these specific contracts. Three checks catch the entire batch:

  1. Tesla and Musk-affiliated entities do not have an ERC-20 token. Any token named Optimus / Tesla / SpaceX / xAI / Boring Company on Ethereum is by definition not affiliated with them. Same rule for any AI / robotics company that has not publicly announced a token launch via SEC or regulatory filing.
  2. Always simulate the sell, not just the buy. Scanners that only check the buy will pass the slightly cleaner OPTIMUS variants. RektRadar runs both buy and sell simulations on every analysis - the buy_failed / sell_failed flag pair is the only reliable honeypot indicator at scale.
  3. Check the deployer history. A wallet that just shipped its first contract three days ago, holds 100% of the LP, and has fifteen near-identical sibling contracts on the same chain is a factory operation. The new_wallet + creator_holds_all_lp combo, plus 5+ sibling contracts from the same deployer cluster, is enough on its own to walk away.

The full catalog

Screenshot of the public /scam/OPTIMUS hub page on app.rektradar.io listing all OPTIMUS-symbol scam contracts detected by RektRadar. Each row shows the contract address, the token name Optimus Prime, the analyzed risk score in a coloured RISK badge (red for 80+, orange for 50-79, yellow for under 50), and a quick-scan call-to-action button.

You can scan any OPTIMUS variant on the $OPTIMUS scam tokens catalog on Ethereum - the data is fresh and free.

We will keep documenting these waves as they happen. Whatever Musk meme trends next, the next factory will spin up and ship seventeen contracts in nine hours. Only the brand changes.

A note on detection: this entire factory was caught by the same scam-detection pipeline that catches the trickle of one-off rugs - no special-casing for the Optimus brand. The factory pattern emerges by itself when the analyzer flags 17 sibling contracts with overlapping flags, all from new deployer wallets, all within hours of each other. That structural signal is what makes brand-jack factories tractable at scale.