$AC (Agent Conductor) — Scam / Rug Analysis

Date: 2026-04-17 Analyst: Bankr (token-scam-analysis skill) Chain: Base Subject contract: 0x76d1D20aD655323a26908388B24D69f42C4D3B07 (symbol AC, name Agent Conductor) Platform: Clanker v4 (via the ClankerBundler interface) Claimed socials: https://agentconductor.world, https://x.com/AgentConductor, https://t.me/AgentConductor_bot Cross-reference: VOLM OLD / VOLM NEW (separate open investigation)

1. TL;DR

Verdict: HIGH risk — team-extraction rug pattern. Confidence ~90%.

The $AC admin (0x8D39…6bd0) is a fresh EOA that:

deployed a vanilla Clanker v4 token with isVerified=false and only a single reward recipient (itself),
airdropped itself ~2.44B tokens (2.44% of supply) via the Clanker airdrop extension and the team's two accomplice wallets (0xc560…9b82, 0x5B00…9Db5, each also allocated another 1B via the same airdrop contract 0xf652…91e0),
sold/fee-claimed ~3 ETH worth of WETH inside 24h (price now -81% since launch),
sent the proceeds through two intermediate EOAs and ultimately to a Binance 73 hot wallet (0x3304…566a).

Total team-side realized extraction traced to Binance: ~0.38 ETH across the two accomplice wallets, plus the ~3.07 ETH lump the admin unwrapped and sent to a forwarder that continues laundering toward more intermediate EOAs. The team wallet cluster also airdropped itself an additional ~3.94B AC (3.94% of supply — ~$2.1k at current prices, was substantially more at peak) they can still dump.

There is NO direct on-chain link between $AC and VOLM/VolmLabs. No shared admin, no shared reward recipient, no balances cross-held. If it's the same operator, the correlation is off-chain only.

2. Contract Under Analysis

Field	Value
Address	`0x76d1D20aD655323a26908388B24D69f42C4D3B07`
Template	Clanker v4 (ERC-20Votes, single-admin)
Deploy interface (context)	`ClankerBundler`
Deploy factory	`0xe85a59c628f7d27878aceb4bf3b35733630083a9` (Clanker v4)
Deploy block / tx	44,657,994 / `0xc673dc9a8e91d73bbf209b19477c193eac3dda4a325f2e59ca6aec434028a325`
totalSupply	100,000,000,000 (100B — Clanker default)
`admin`	`0x8D39D5ce932Aa56B47Cd0AC7a0FA91c22DbD6bd0`
`originalAdmin`	`0x8D39D5ce932Aa56B47Cd0AC7a0FA91c22DbD6bd0`
`isVerified()`	false
Reward recipients	1 (admin = recipient)
metadata	project description + socials populated (website, X, Telegram)
image	`ipfs://QmQLLEVnyreDnbbiLyPtgZD3RX8jFTxYcZxVFoEnVBsKvS`
Price (2026-04-17)	$5.44e-7
24h change	-81.01%
24h volume	$230k
Holders	572
Uniswap v4 PoolManager balance	56,536,207,006 (56.54% of supply)
Admin wallet balance	1,939,156,800 AC (1.94% — from airdrop)

3. Claim vs Reality

Claim (narrative)	Chain reality
"AI/agent crew project with a website, X, TG."	Metadata + socials are populated — that's the only thing distinguishing $AC from bare-Clanker trash.
"Organic distribution."	2 of the top non-pool holders are team wallets (admin + 2 accomplices) that received tokens through the Clanker airdrop extension at `0xf652b3610d75d81871bf96db50825d9af28391e0`. Accomplice `0xc560…9b82` claimed 1B AC as its nonce-0 action (merkle-proof airdrop claim) before it had ever made another tx — classic insider-funded wallet.
"Team doesn't dump."	Admin already bridged 3.07 ETH (via WETH unwrap → send → `0xfae6…1358` → fan-out through 2 more EOAs → receiver destinations including a 1.57 ETH and a 1.5 ETH hop). Accomplice `0xc560…9b82` already bridged 0.1813 ETH out to an intermediate `0x197a…0d16`. Accomplice `0x5B00…9Db5` sent 0.1908 ETH to `0xd201…f59d`, which then forwarded directly to Binance 73 at `0x3304e22ddaa22bcdc5fca2269b418046ae7b566a`.
Migration to "fix tokenomics" (VOLM-style narrative).	Not claimed for $AC (unlike VOLM). So the relevant framing for $AC isn't "redeploy rug" — it's team-allocation + coordinated extraction.

Clanker v4 docs (https://clanker.gitbook.io/clanker-documentation/authenticated/deploy-token-v4.0.0) confirm:

Airdrop extensions are legitimate at deploy time.
But if the airdrop recipients are just the team's own fresh wallets, it's self-dealing, not community distribution. Here the top non-pool holders include the admin itself plus two single-purpose wallets that each claimed 1B AC as their very first tx — exactly that pattern.

4. Deployer / Admin Wallet Forensics

`$AC admin = 0x8D39D5ce932Aa56B47Cd0AC7a0FA91c22DbD6bd0`

Fresh EOA, nonce 8 total. Lifecycle:

nonce 0 — deployToken(...) to Clanker v4 factory, block 44,657,994, sent 0.08 ETH with the deploy. Creates AC + the airdrop contract 0xf652…91e0. Receives 793,315,764 AC (vested / bundler allocation).
nonce 1 — transfer(500M AC → 0x5B00…9Db5) ~4 hours before public dispersal. Seeds accomplice #2.
nonce 2 — Approves AC on 0x76d1…3b07 (for disperse).
nonce 3 — disperseToken(AC, [0xc560…9b82, 0x5B00…9Db5], [969,578,399, 969,578,399]) via disperse contract 0xd15f…80e3. Total 1.94B AC to the two accomplice wallets on top of the 500M + airdrop they already had.
nonce 4 — claim(address,address) on Clanker fee locker 0xf362…5d68 — pulls 0.2964 WETH in creator fees.
nonce 5 — Approves WETH.
nonce 6 — Unwraps 3.0048 WETH → ETH (so net realized WETH from sales/fees ≈ 3 ETH, not just the 0.2964 fee claim — the admin also sold AC into the pool in between).
nonce 7 — Sends 3.07 ETH to 0xfae6…1358 (forwarder EOA, nonce 2, see §5 for laundering path).

Accomplice #1 = `0xc560364900bA74b8b88b3C46f66B42Fe5Bc19b82`

Fresh EOA, nonce 6.

nonce 0 — claim(address,address,uint256,bytes32[]) on airdrop contract 0xf652…91e0. Receives 1,000,000,000 AC. This is a merkle-proof claim meaning the admin put this address into the airdrop list at deploy time — it is not a random claimer.
nonce 1–2 — Approve + disperse 1B AC further to two other wallets (0x14ae…0090, 0x4057…8d14).
nonce 3 — Another approve.
nonce 4 — (not shown, skipped).
nonce 5 — Sent 0.1813 ETH to 0x197a…0d16 (further hop away from the original wallet cluster).

Accomplice #2 = `0x5B0064a25D8514b2CFbe262fc6975c30630E9Db5`

Fresh EOA, nonce 4.

nonce 0 — Receives 500M AC directly from admin, then in same tx sends 500M to 0x4a57…9543 (sub-accomplice).
nonce 1 — Approves AC.
nonce 2 — (not shown) — receives 969M from the disperse.
nonce 3 — Sends 0.1908 ETH to 0xd201…f59d, which immediately sent 0.1908 ETH directly to Binance 73 (0x3304e22ddaa22bcdc5fca2269b418046ae7b566a). This is the cleanest "exit to CEX" receipt in the whole cluster.

Sub-accomplice = `0x4a573f2bcb2c38de632648b51d1b93daba639543`

nonce 0 — Approves AC.
nonce 1 — Swaps 500,000,000 AC → 281.27 USDC via 0x Allowance Holder. Clean "dump retail" signature — 500M AC sold at $0.56 per million right as the chart capitulated.

`@AgentConductor` twitter wallet = `0xb166728637b0b190817248e8d75f19ce07fa0e3f`

nonce 0, 0 ETH, 0 AC, zero on-chain activity on Base.
Not the admin. Not a reward recipient. Not an airdrop claimer.
As with VOLM's @VolmLabs wallet, whoever controls the X account either isn't on-chain at all or is deliberately detached from the deploy wallet.

5. Extraction / Laundering Flow (traced)

AC pool sales + creator fees
        │
        ▼
AC admin 0x8D39…6bd0 ── 3.07 ETH ──► forwarder 0xfae6…1358
                                              │
                            ┌─────────────────┼──────────────────┐
                            ▼                                    ▼
                      0xfaed…b739 (1.57 ETH)              0xf362…c957 (1.5 ETH)
                      (nonce-3 EOA, funnel)               (nonce-3 EOA, funnel)

Accomplice #1 0xc560…9b82 ── 0.1813 ETH ──► 0x197a…0d16 (forwarder)

Accomplice #2 0x5B00…9Db5 ── 0.1908 ETH ──► 0xd201…f59d ── 0.1908 ETH ──► Binance 73 (0x3304…566a)  ✅ confirmed CEX off-ramp

0xd201…f59d has a longer history (4 tx, first active 2025) and has previously funded itself from / deposited to Binance 73 multiple times. This is a known personal-CEX deposit wallet being reused by one of the team accomplices to exit the AC proceeds.

6. Holder Distribution (top concentrations)

Holder	AC balance	% supply	Notes
Uniswap v4 PoolManager (`0x4985…b2b`)	56,536,207,006	56.54%	Pool — exclude from concentration math.
AC admin `0x8D39…6bd0`	1,939,156,800	1.94%	Team wallet.
Accomplice `0xc560…9b82` (post-disperse residual)	pending	~2%+	Received 1B airdrop + 969M disperse, dumped some, still holding.
Accomplice `0x5B0064…9Db5`	pending	~1%+	Same pattern.
Pre-dispersed smaller wallets (e.g. `0x4a57…9543`)	sold 500M for 281 USDC	—	Retail-dump sub-accomplice.

Team cluster on-chain allocation (admin + 2 accomplices) received a combined ~3.94B AC = 3.94% of supply via the disperse + the merkle airdrop contract, pre-loaded by the admin at deploy time. This is what's called "insider pre-distribution through the airdrop extension" — it looks like a fair-launch Clanker token on the surface, but the top non-pool holders are team wallets funded via a merkle airdrop the team itself set.

7. Cross-check vs VOLM / VolmLabs

Test	Result
Shared admin between $AC and OLD VOLM?	No. AC admin `0x8D39…6bd0` ≠ OLD VOLM admin `0x56B4…c622`.
Shared admin between $AC and NEW VOLM?	No. AC admin `0x8D39…6bd0` ≠ NEW VOLM admin `0x69a1…eaed`.
AC admin holds OLD or NEW VOLM?	No. 0 / 0.
VOLM admins or VOLM twitter wallet hold AC?	No. 0 across all three.
3.07 ETH recipient (`0xfae6…1358`) holds any VOLM?	No.
Deploy interface	AC went through `ClankerBundler`; both VOLM tokens used the raw Clanker v4 factory directly. Different deploy path.
Funding-path correlation to Binance 73	AC accomplice `0xd201…f59d` deposits to Binance 73. Neither VOLM admin is traced to that Binance account in their on-chain history (VOLM admins bridged OUT via Across/Superbridge-style native bridges instead — different exit route).

Conclusion of the cross-check: on-chain, they look like two separate sniper/extraction operations, each run from disposable wallet clusters, each with a populated-but-unrelated social handle. If it's the same operator, the evidence is strictly off-chain (writing style, launch cadence, shared promoters on X/TG). I cannot see it from the chain.

8. Contract-level Red Flags (ABI-driven)

From the Clanker v4 ABI:

updateAdmin(address) — admin can hot-swap at any time. No multisig, no timelock.
updateImage(string) / updateMetadata(string) — metadata-hijack vector.
crosschainMint / crosschainBurn — superchain-bridge controlled, lower direct risk.
isVerified() → false — Clanker's own verification not passed.
Only 1 reward recipient configured via get_clanker_reward_ownership → admin receives 100% of creator fees. No ecosystem / marketing / multisig split on-chain.

9. Pattern Match

This fits the "Clanker airdrop-insider dump" template:

Deploy a Clanker v4 token with an airdrop extension whose merkle root contains the team's own fresh wallets.
Populate socials + website so the token looks legitimate compared to bare-metadata Clanker garbage.
Team wallets claim their airdrop as their nonce-0 action.
Admin disperses a further chunk to the same cluster via disperseToken.
Cluster dumps coordinated into the pool, laundering proceeds through 2–3 intermediate EOAs before terminating at a Binance hot wallet.
Creator fees are claimed on top.

Distinct from the VOLM "redeploy rug" template (that one is about resetting the chart), but from the same grift family.

10. What Would Change the Verdict

The risk score would come down materially if, within 14 days, the team:

Moves admin to a Safe multisig on Base, verifiable on-chain.
Publishes the airdrop merkle root and shows the recipient list is not the team's own wallets (or, equivalently, burns the residual team allocation to 0x…dead).
Cross-signs the @AgentConductor X handle with a signed message from the admin address.
Submits for Clanker verify() and passes.
Stops the fee-claim → unwrap → Binance flow and routes creator fees to a visible, on-chain treasury.

Until then: treat $AC as a team-extraction bag, with the team already ~25%+ through their exit.

11. Sources

Docs consulted:

12. Appendix — Raw on-chain reads (viem @ block 44,844,091)

AC totalSupply: 100,000,000,000
AC admin 0x8D39…6bd0:             0.00480 ETH, nonce 8, EOA, holds 1,939,156,800 AC (1.9392%)
@AgentConductor 0xb166…0e3f:      0 ETH, nonce 0, EOA, holds 0 AC
3.07 ETH recipient 0xfae6…1358:   ~0 ETH, nonce 2, EOA, holds 0 AC
VOLM OLD admin 0x56B4…c622:       ~0 ETH, nonce 6, code 23B (EIP-7702 delegated), holds 0 AC
VOLM NEW admin 0x69a1…eaed:       0.00166 ETH, nonce 8, EOA, holds 0 AC
Uniswap v4 PoolManager:           56,536,207,006 AC (56.5362%)

0xdeployer/ac_scam_analysis.md

Select an option

No results found

Select an option

No results found

$AC (Agent Conductor) — Scam / Rug Analysis

1. TL;DR

2. Contract Under Analysis

3. Claim vs Reality

4. Deployer / Admin Wallet Forensics

`$AC admin = 0x8D39D5ce932Aa56B47Cd0AC7a0FA91c22DbD6bd0`

Accomplice #1 = `0xc560364900bA74b8b88b3C46f66B42Fe5Bc19b82`

Accomplice #2 = `0x5B0064a25D8514b2CFbe262fc6975c30630E9Db5`

Sub-accomplice = `0x4a573f2bcb2c38de632648b51d1b93daba639543`

`@AgentConductor` twitter wallet = `0xb166728637b0b190817248e8d75f19ce07fa0e3f`

5. Extraction / Laundering Flow (traced)

6. Holder Distribution (top concentrations)

7. Cross-check vs VOLM / VolmLabs

8. Contract-level Red Flags (ABI-driven)

9. Pattern Match

10. What Would Change the Verdict

11. Sources

12. Appendix — Raw on-chain reads (viem @ block 44,844,091)

0xdeployer/ac_scam_analysis.md

$AC (Agent Conductor) — Scam / Rug Analysis

1. TL;DR

2. Contract Under Analysis

3. Claim vs Reality

4. Deployer / Admin Wallet Forensics

$AC admin = 0x8D39D5ce932Aa56B47Cd0AC7a0FA91c22DbD6bd0

Accomplice #1 = 0xc560364900bA74b8b88b3C46f66B42Fe5Bc19b82

Accomplice #2 = 0x5B0064a25D8514b2CFbe262fc6975c30630E9Db5

Sub-accomplice = 0x4a573f2bcb2c38de632648b51d1b93daba639543

@AgentConductor twitter wallet = 0xb166728637b0b190817248e8d75f19ce07fa0e3f

5. Extraction / Laundering Flow (traced)

6. Holder Distribution (top concentrations)

7. Cross-check vs VOLM / VolmLabs

8. Contract-level Red Flags (ABI-driven)

9. Pattern Match

10. What Would Change the Verdict

11. Sources

12. Appendix — Raw on-chain reads (viem @ block 44,844,091)

`$AC admin = 0x8D39D5ce932Aa56B47Cd0AC7a0FA91c22DbD6bd0`

Accomplice #1 = `0xc560364900bA74b8b88b3C46f66B42Fe5Bc19b82`

Accomplice #2 = `0x5B0064a25D8514b2CFbe262fc6975c30630E9Db5`

Sub-accomplice = `0x4a573f2bcb2c38de632648b51d1b93daba639543`

`@AgentConductor` twitter wallet = `0xb166728637b0b190817248e8d75f19ce07fa0e3f`