Data correction: unrelated Ethereum vault hack is misattributed to YieldCore.App

[marvz702]

Incorrect attribution

The hack currently associated with the DefiLlama profile at https://defillama.com/protocol/yieldcore was not an incident involving YieldCore.App, its BSC contracts, or its users.

The apparent association is a name collision with an independently deployed vault named yieldcore-3rd-deal.

On-chain evidence

Reported incident

• Network: Ethereum mainnet
• Asset: USDC
• Vault: 0xb9c7c84a1aa0dd40b5b38aae815ad0cdd2e5f88a
• Incident transaction: https://etherscan.io/tx/0x6b04344d5627df59d3bc645e7454f4605a90272852a91e435e370376643353b3
• The vault directory identifies its protocol as unknown / not yet identified, with no YieldCore.App homepage or protocol association:
  https://tradingstrategy.ai/vaults/yieldcore-3rd-deal
• Independent incident analysis says the affected component should be tracked as the specific third-party vault rather than as a confirmed compromise of a broader protocol core:
  https://blog.autosec.dev/security-events/YieldCore-3rd-deal-vault-authorization-exploit/

YieldCore.App tracked by DefiLlama

• Website: https://yieldcore.app
• Network: BNB Smart Chain
• Asset backing bonds: USDT
• Active V4.3.2 Core: 0x903407687486b3ae60746622D06b2eD3D75EaCAb
• Legacy V4.3.1 Core: 0x6D6CDf89Cc565A04f0Ba99A1Dc13d43d0d005E4E
• Legacy V3 Core: 0x2375Fcc2a256425228aA94d7100093230761639e
• TVL restoration/update: fix: restore YieldCore TVL with V4.3.2 Core #20767

None of the YieldCore.App addresses above is the Ethereum vault involved in the incident. The chains, denomination assets, and contract addresses are different.

Requested correction

1. Remove the April 28, 2026 / approximately $398K hack association from the DefiLlama yieldcore protocol profile.
2. Remove https://yieldcore.app and the BSC YieldCore protocol description from that hack record.
3. Retain the historical incident, if desired, under a neutral name such as “yieldcore-3rd-deal (unidentified third-party Ethereum vault)”, using the actual Ethereum vault address.
4. Ensure the refreshed YieldCore profile associated with fix: restore YieldCore TVL with V4.3.2 Core #20767 states that no known hack is attributed to YieldCore.App.

This request does not ask DefiLlama to suppress a genuine incident. It asks that the incident be attributed to the contract and entity evidenced by the on-chain record rather than to an unrelated protocol with a similar name.