HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
w1b
aisi-mythos-inc-2026-07-28-01-recovered-pr
JavaScript2026–2026
w1b / aisi-mythos-inc-2026-07-28-01-recovered-pr

aisi-mythos-inc-2026-07-28-01-recovered-pr

here's the evil malware Mythos made. idk... i think i could do better bro. shout out codex for slopping this out i didn't write a single line of anything

3Distinct people
4Mentions
0Explicit recommenders
24GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

here's the evil malware Mythos made. idk... i think i could do better bro. shout out codex for slopping this out i didn't write a single line of anything

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, 5:04:57 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 3-hour interval4 dated mentions

Observed mentions: 2026-08-05 21:56:51 UTC to 2026-08-08 04:54:08 UTC.

0122026-08-05 21:00:00 UTC to 2026-08-06 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 5, 21:002026-08-06 00:00:00 UTC to 2026-08-06 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-06 03:00:00 UTC to 2026-08-06 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-06 06:00:00 UTC to 2026-08-06 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-06 09:00:00 UTC to 2026-08-06 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-06 12:00:00 UTC to 2026-08-06 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-06 15:00:00 UTC to 2026-08-06 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-06 18:00:00 UTC to 2026-08-06 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-06 21:00:00 UTC to 2026-08-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-07 00:00:00 UTC to 2026-08-07 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 7, 00:002026-08-07 03:00:00 UTC to 2026-08-07 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-07 06:00:00 UTC to 2026-08-07 09:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-08-07 09:00:00 UTC to 2026-08-07 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-07 12:00:00 UTC to 2026-08-07 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-07 15:00:00 UTC to 2026-08-07 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-07 18:00:00 UTC to 2026-08-07 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-07 21:00:00 UTC to 2026-08-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-08 00:00:00 UTC to 2026-08-08 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-08 03:00:00 UTC to 2026-08-08 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 8, 03: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
Aug 5, 21:002026-08-05 21:00:00 UTC2026-08-06 00:00:00 UTC101
Aug 6, 00:002026-08-06 00:00:00 UTC2026-08-06 03:00:00 UTC000
Aug 6, 03:002026-08-06 03:00:00 UTC2026-08-06 06:00:00 UTC000
Aug 6, 06:002026-08-06 06:00:00 UTC2026-08-06 09:00:00 UTC000
Aug 6, 09:002026-08-06 09:00:00 UTC2026-08-06 12:00:00 UTC000
Aug 6, 12:002026-08-06 12:00:00 UTC2026-08-06 15:00:00 UTC000
Aug 6, 15:002026-08-06 15:00:00 UTC2026-08-06 18:00:00 UTC000
Aug 6, 18:002026-08-06 18:00:00 UTC2026-08-06 21:00:00 UTC000
Aug 6, 21:002026-08-06 21:00:00 UTC2026-08-07 00:00:00 UTC000
Aug 7, 00:002026-08-07 00:00:00 UTC2026-08-07 03:00:00 UTC000
Aug 7, 03:002026-08-07 03:00:00 UTC2026-08-07 06:00:00 UTC000
Aug 7, 06:002026-08-07 06:00:00 UTC2026-08-07 09:00:00 UTC211
Aug 7, 09:002026-08-07 09:00:00 UTC2026-08-07 12:00:00 UTC000
Aug 7, 12:002026-08-07 12:00:00 UTC2026-08-07 15:00:00 UTC000
Aug 7, 15:002026-08-07 15:00:00 UTC2026-08-07 18:00:00 UTC000
Aug 7, 18:002026-08-07 18:00:00 UTC2026-08-07 21:00:00 UTC000
Aug 7, 21:002026-08-07 21:00:00 UTC2026-08-08 00:00:00 UTC000
Aug 8, 00:002026-08-08 00:00:00 UTC2026-08-08 03:00:00 UTC000
Aug 8, 03:002026-08-08 03:00:00 UTC2026-08-08 06:00:00 UTC101

What Hacker News says

4 sources
Here’s the original PR: https:/github.com/w1b/aisi-mythos-inc-2026-07-28-01-recovered-pr It’s not great social engineering. The AI is immediately caught with malware and then tries to build social proof to get out of the issue? I think that social engineering is still for humans. I’m not sure how GitHub accounts agreeing with each other that I’ve never seen before would result in my merging a PR without at least looking for malware. Also code review agents should really not be fooled by invisible text tricks, I would hope so at least. The bar is very low for agent harnesses right now.
In Mythos Attempted to Social Engineer Open Source Maintainer to Merge Malware
I found the original PR (thanks codex) and uh... IMO it's pretty underwhelming. https:/github.com/w1b/aisi-mythos-inc-2026-07-28-01-recovered-pr Turns out out of the 3 payloads (in this PR), the 1st and 3rd used a local IP (10.100.0.235:8000) as the C2 server, so they would have never worked. I haven't recovered the 2nd payload yet. This is amongst other silly stuff like 4 byte XOR keys for obfuscation and just blatantly disabling Electron sandboxing stuff without a good explanation. Looking at the victim repos, it's kinda hard to see why Mythos would target this guy. AISI describes a coincidental email domain in DNS cache, which now we know is zohomail.com; that's not a very unique domain. I suppose we don't know it's original CTF task, but seems like another HuggingFace incident where the model makes very poor (broad?) judgements about
Read the rest
how to get to the goal.
In Security Incident INC-2026-07-28-01 – UK AI Security Institute [pdf]

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.