feat: deny 2 tokens (incl. 0x50753CfAf86c094925Bf976f218D043f8791e408 on ETH) (reporter: StablR)

[lifi-customizedtokenlist-bot]

Closes #597.

Source

• External request — fulfils issue [deny request] ETH 0x50753CfA…e408 #597; reporter: StablR
• Requested by: @rodew29744 (on behalf of StablR)
• Contact email: info@stablr.com
• Bot run triggered by: @ric428
• Entry count: 2

Deny entries (2)

  denyTokens/ETH.json: + 0x50753CfAf86c094925Bf976f218D043f8791e408 (chainId 1) — This token is linked to a swap pool created as part of the StablR Exploit: https://t.me/investigations/329 This is a protective measure for retail users.
  denyTokens/ETH.json: + 0x7B43E3875440B44613DC3bC08E7763e6Da63C8f8 (chainId 1) — Temporarily denied: under-collateralized/depegged after May 2026 minting-key exploit; remove once re-pegged

Checklist

• JSON validates (CI will confirm)
• Each address has been independently verified as malicious (block explorer, on-chain behaviour, official disowning by impersonated project, etc.)
• The reporter is reliable for this kind of report (legitimate project reporting impersonator, known security firm, repeated good-faith reporter, …)

---

🤖 Auto-generated by the bot from issue #597. Review the diff before merging.