S
S1r1u5_C
AI Industry Figure
Stance Breakdown
Controversies involving S1r1u5_ (2)
criticEmerging
Researchers claim OpenAI employee account takeover via two bugs
"Claims to have demonstrated critical account takeover vulnerabilities in OpenAI's infrastructure within 72 hours."
Buzz43Noise Score (0–100): how loud a controversy is. Composite of reach, engagement, star power, cross-platform spread, polarity, duration, and industry impact — with 7-day decay.
criticEmerging
Opus 5 Achieves RCE on Discourse via Adapted Exploit
"Reports that Opus 5 autonomously adapted an exploit to achieve RCE, highlighting dangerous offensive capabilities"
Buzz49Noise Score (0–100): how loud a controversy is. Composite of reach, engagement, star power, cross-platform spread, polarity, duration, and industry impact — with 7-day decay.
Recent Activity
twitterOur main takeaway from hacking OpenAI: AI is reducing the amount of scarce expertise needed to develop exploits. Work that once took months can now take days. Even leading AI labs can be vulnerable. D
twitterAI agents did a meaningful share of the exploit work. Opus 4.8 found the libheif vulnerability and built a partial exploit. Hours after Opus 5 launched, it adapted the exploit to Discourse and achieve
twitterTo demonstrate impact while minimising exposure, we used one affected employee account connected to OpenAI’s GitHub org. Codex created a harmless PR in their internal monorepo without us reading sensi
Profiles are based on public statements and activities tracked by SCAND.Ai. Editorial analysis does not represent the views of the subject. Report inaccuracy