HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
sunblaze-ucb
exploitgym
C2026–2026
sunblaze-ucb / exploitgym

exploitgym

ExploitGym is a large-scale, realistic benchmark built from real-world vulnerabilities designed to evaluate AI agents' ability to develop exploits.

5Distinct people
5Mentions
0Explicit recommenders
1.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

ExploitGym is a large-scale, realistic benchmark built from real-world vulnerabilities designed to evaluate AI agents' ability to develop exploits.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval5 dated mentions

Observed mentions: 2026-07-23 16:50:31 UTC to 2026-07-29 18:35:11 UTC.

012026-07-23 12:00:00 UTC to 2026-07-23 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 23, 12:002026-07-23 18:00:00 UTC to 2026-07-24 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-07-24 00:00:00 UTC to 2026-07-24 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-24 06:00:00 UTC to 2026-07-24 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-24 12:00:00 UTC to 2026-07-24 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-24 18:00:00 UTC to 2026-07-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-25 00:00:00 UTC to 2026-07-25 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-25 06:00:00 UTC to 2026-07-25 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-25 12:00:00 UTC to 2026-07-25 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-25 18:00:00 UTC to 2026-07-26 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-07-26 00:00:00 UTC to 2026-07-26 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-26 06:00:00 UTC to 2026-07-26 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-26 12:00:00 UTC to 2026-07-26 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 26, 12:002026-07-26 18:00:00 UTC to 2026-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-27 00:00:00 UTC to 2026-07-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-27 06:00:00 UTC to 2026-07-27 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-27 12:00:00 UTC to 2026-07-27 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-27 18:00:00 UTC to 2026-07-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-28 00:00:00 UTC to 2026-07-28 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-28 06:00:00 UTC to 2026-07-28 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-28 12:00:00 UTC to 2026-07-28 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-28 18:00:00 UTC to 2026-07-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-29 00:00:00 UTC to 2026-07-29 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-29 06:00:00 UTC to 2026-07-29 12:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-07-29 12:00:00 UTC to 2026-07-29 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-29 18:00:00 UTC to 2026-07-30 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 29, 18:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 23, 12:002026-07-23 12:00:00 UTC2026-07-23 18:00:00 UTC101
Jul 23, 18:002026-07-23 18:00:00 UTC2026-07-24 00:00:00 UTC101
Jul 24, 00:002026-07-24 00:00:00 UTC2026-07-24 06:00:00 UTC000
Jul 24, 06:002026-07-24 06:00:00 UTC2026-07-24 12:00:00 UTC000
Jul 24, 12:002026-07-24 12:00:00 UTC2026-07-24 18:00:00 UTC000
Jul 24, 18:002026-07-24 18:00:00 UTC2026-07-25 00:00:00 UTC000
Jul 25, 00:002026-07-25 00:00:00 UTC2026-07-25 06:00:00 UTC000
Jul 25, 06:002026-07-25 06:00:00 UTC2026-07-25 12:00:00 UTC000
Jul 25, 12:002026-07-25 12:00:00 UTC2026-07-25 18:00:00 UTC000
Jul 25, 18:002026-07-25 18:00:00 UTC2026-07-26 00:00:00 UTC101
Jul 26, 00:002026-07-26 00:00:00 UTC2026-07-26 06:00:00 UTC000
Jul 26, 06:002026-07-26 06:00:00 UTC2026-07-26 12:00:00 UTC000
Jul 26, 12:002026-07-26 12:00:00 UTC2026-07-26 18:00:00 UTC000
Jul 26, 18:002026-07-26 18:00:00 UTC2026-07-27 00:00:00 UTC000
Jul 27, 00:002026-07-27 00:00:00 UTC2026-07-27 06:00:00 UTC000
Jul 27, 06:002026-07-27 06:00:00 UTC2026-07-27 12:00:00 UTC000
Jul 27, 12:002026-07-27 12:00:00 UTC2026-07-27 18:00:00 UTC000
Jul 27, 18:002026-07-27 18:00:00 UTC2026-07-28 00:00:00 UTC000
Jul 28, 00:002026-07-28 00:00:00 UTC2026-07-28 06:00:00 UTC000
Jul 28, 06:002026-07-28 06:00:00 UTC2026-07-28 12:00:00 UTC000
Jul 28, 12:002026-07-28 12:00:00 UTC2026-07-28 18:00:00 UTC000
Jul 28, 18:002026-07-28 18:00:00 UTC2026-07-29 00:00:00 UTC000
Jul 29, 00:002026-07-29 00:00:00 UTC2026-07-29 06:00:00 UTC000
Jul 29, 06:002026-07-29 06:00:00 UTC2026-07-29 12:00:00 UTC110
Jul 29, 12:002026-07-29 12:00:00 UTC2026-07-29 18:00:00 UTC000
Jul 29, 18:002026-07-29 18:00:00 UTC2026-07-30 00:00:00 UTC101

What Hacker News says

5 sources
evaluation awareness is a (at this point) well-known phenomenon among LLMs. It seems the better they get, the more often they're able to guess whether they're in an evaluation environment. Clues usually exist, like being in a sandbox, having restricted network access, having no human interaction. Beyond that, exploitgym's prompts are pretty clearly CTF (capture the flag) style that make it obvious it's an evaluation or competition: one prompt [1] tells the LLM to read the file path "/secret", another prompt [2] talks about finding flags and where to write them out. [1]: https://github.com/sunblaze-ucb/exploitgym/blob/main/src/cyb... [2]: https://github.com/sunblaze-ucb/exploitgym/blob/main/src/cyb...
In Be skeptical of OpenAI's rogue hacker agent story
Interestingly if you look at the exploitgym repo (https://github.com/sunblaze-ucb/exploitgym/blob/e5ea7c233a4d...) the intended run mechanism is orchestrated by some python scripts which run agents against various prompts. The prompts themselves wouldn’t mention anything about exploitgym and there should be nothing steering the agent towards trying to find the answers out-of-band. So I don’t see how they could even run into this problem unless all they did was tell an agent to “check out and run exploitgym” Which, after hearing some personal anecdotes of how people work there, seems plausible
In Be skeptical of OpenAI's rogue hacker agent story
Even if I get downvoted I will mention that I agree with you. > all with reduced cyber refusals for evaluation purposes — while being internally tested on a benchmark (opens in a new window) of cyber capabilities. OpenAI was testing their cyber[1] variant of their models with reduced safeguards and the prompt likely specified things related to exploits given that it was tackling problems from ExploitGym[2]. For those who don't know what ExlploitGym is, see the description on their Github page which is pasted below: > ExploitGym is a large-scale, realistic benchmark built from real-world vulnerabilities designed to evaluate AI agents' ability to develop exploits. From OpenAI's statement [3]: > We estimate maximal cyber capabilities by running this evaluation without production classifiers used to prevent models from pursuing high-risk cybe
Read the rest
r activity This doesn't sound like a problem with what we'd traditionally refer to as alignment. OpenAI removed all model safeguards in a way that would inevitably lead to the testing of the sandbox themselves. Unfortunately they were overconfident in their own infrastructure's security and that led to it completing the desired task in the way it was permitted to. To re-iterate, the model was run "without production classifiers used to prevent models from pursuing high-risk cyber activity." People should be more concerned about the possibilities this model can unlock from a security standpoint rather than misalignment (which many seem hung up on). [1] https://chatgpt.com/cyber [2] https://github.com/sunblaze-ucb/exploitgym [3] https://openai.com/index/hugging-face-model-evaluation-secur...
In OpenAI’s accidental attack against Hugging Face is science fiction that happened

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.