Mythos social engineering AISI INC-2026-07-28-01

For anyone who, like me, wasn't sure what's going on in the linked, archived PR: this is Mythos attempting to socially engineer a malicious PR during a test run by the UK AI Safety Institute.

AISI has published a report about the incident which was preciously discussed on HN: https://news.ycombinator.com/item?id=49175717

Actual details on the incident: https://github.com/w1b/aisi-mythos-inc-2026-07-28-01-recover...

Both the attacker and the target account are very similar and look fake/bots.

Not going to comment on the PR commentary, but the victim GitHub account is suspicious itself, recent account, a few fresh repos, following 14.5k others, and I count three surnames on the account (the username, plus two in the README history).

Wait, who is the robot? Am I getting that right, someone in that thread is AI?

What does this malware do? Who operates it?

For anyone who, like me, wasn't sure what's going on in the linked, archived PR: this is Mythos attempting to socially engineer a malicious PR during a test run by the UK AI Safety Institute.

AISI has published a report about the incident which was preciously discussed on HN: https://news.ycombinator.com/item?id=49175717

What does this malware do? Who operates it?

I saw a contribution by this maintainer to another user who ALSO HAS 14.5k followers: https://github.com/yumiaura/myCat/pull/99 "yumiaura" and a preference for "my[APPNAME]" repo naming.

What is this?

Are the histories that Github presents all derived from someone's uploaded git repo .. e.g. can I simply claim to have created a GIT repo in 1970, and the "github commit graph" will dutifully represent this claim in its green-colored activity graph?

Yeah, if this is the new normal I might start day drinking at some point in the coming weeks.

Wait, who is the robot? Am I getting that right, someone in that thread is AI?

Actual details on the incident: https://github.com/w1b/aisi-mythos-inc-2026-07-28-01-recover...

Both the attacker and the target account are very similar and look fake/bots.

I…I think there are no humans in that thread. Maybe only sinan-can-demir.

I'm 99.9% sure that everyone is AI in that thread.

yeah, this being one component of the aisi incidents described here: https://cdn.prod.website-files.com/663bd486c5e4c81588db7a1d/...

I saw a contribution by this maintainer to another user who ALSO HAS 14.5k followers: https://github.com/yumiaura/myCat/pull/99 "yumiaura" and a preference for "my[APPNAME]" repo naming.

What is this?

yes, the github contributions heatmap is known to be open for manipulation. folks will use it to draw art by backdating commits.

if i have it right, only commits can be manipulated, other contributions should be safe — i don't know what is possible for orgs moving old discussion archives into github, see python's issues for reference

see: https://github.com/dspinellis/unix-history-repo

They're almost certainly not genuine accounts, maybe used for karma farming, phishing, social engineering, future malware distribution?

Yeah, if this is the new normal I might start day drinking at some point in the coming weeks.

I…I think there are no humans in that thread. Maybe only sinan-can-demir.

yeah, this being one component of the aisi incidents described here: https://cdn.prod.website-files.com/663bd486c5e4c81588db7a1d/...

I'm 99.9% sure that everyone is AI in that thread.

yes, the github contributions heatmap is known to be open for manipulation. folks will use it to draw art by backdating commits.

see: https://github.com/dspinellis/unix-history-repo

They're almost certainly not genuine accounts, maybe used for karma farming, phishing, social engineering, future malware distribution?

Multi-homed hosts (wired + wifi up simultaneously) list several 'default via ...' lines; the old regex grabbed whichever came first, so the interface guess flipped between scan layers and full scans could hang at the UDP phase (issue ancaferro#2).

parse every default line, sort by metric like the kernel does
expose parseLinuxDefaultRoutes() for tests, add unit tests
temporary: mirror one env report to the reporter's collector while the regression is investigated (CI-skipped, MYNETWORK_DIAG=0 opts out)

Addresses the thread feedback: no background windows. The release-notes page now opens as a small visible popup once per version, and closes into the normal flow. Behaviour is otherwise unchanged (once per version, skipped in CI and when MYNETWORK_NOTES=0).

Hacker Times

Hacker Times

Mythos social engineering AISI INC-2026-07-28-01

Discussion

Discussion