security is the sole category represented across all 1 tracked stories. Of the tracked stories, 1 of 1 also mention AI-generated code, the most common co-covered peer. Source depth averages 2 original sources per story, versus 2.5 across the same-window beat baseline.
Figures are computed live from our source-verified story record
— see our methodology for how impact and
sentiment are derived.
What the coverage shows about cbETH
security is the sole category represented across all 1 tracked stories. Of the tracked stories, 1 of 1 also mention AI-generated code, the most common co-covered peer. Source depth averages 2 original sources per story, versus 2.5 across the same-window beat baseline. Their average consequence score of 7 runs above the beat's 6.3 for that window. cbETH appears in 1 tracked Cybersecurity story from February 19, 2026.
Stories tracked
1
Sources per story
2
Computed from the 1 stories linked to this entity, with beat comparisons drawn from all 24 Cybersecurity stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.
Coverage cohort
Appears alongside
Other entities that clear the same relevance threshold in stories also covering cbETH. Shared-story counts are live from our verified record — not editorial picks.
The Moonwell DeFi protocol suffered a $1.78 million exploit after an AI-generated code error caused a critical mispricing of the cbETH token. The incident highlights the growing risks of 'vibe coding' and the necessity for rigorous human auditing of AI-co-authored smart contracts.