Of course, but the possibly LLM-generated article at 8ksec has no actual preview of even undisclosed proof-of-concept (PoC).
And the article is used as the main source at the Tom’s Hardware article, too.
Therefore, the question is, what is the main point of both the articles, if?:

1. No PoC preview is stated at all;
2. No LLM use is stated in the initial source (at 8ksec);
3. An explicit LLM use at 8ksec is mentioned in the Tom’s Hardware - Mythos by Anthropic;

In other words, it feels more like an ad for Mythos and Apple but based on absolutely no evidence at this point of time, and Mythos is mentioned at Tom’s Hardware article only.

I am sorry, but I didn’t see any actual exploit evidence, but just the ad “groundbreaking” Apple’s MIE and previous CVEs mentioned.

Nor there is any use of LLM/“AI” explicitly stated, too, except the article itself it refers to, which looks like LLM-written: 8ksec.io/mie-deep-dive-enabling-apps [web-archived]

Update (2026-05-17_13-09_0):
- In other words, it feels more like an ad for Mythos and Apple but based on absolutely no evidence at this point of time, and Mythos is mentioned at Tom’s Hardware article only.

Roger that! Thank you for being a developer and improving the ineffably magnificent world! ✨

In this case, we do relatively the same, and usually in database seeding and model factories, I believe, but personally I am more into the Laravel and Symfony, where the mentioned above PHP library is used there under the hood.

Please to stay safe!

Related: https://laravel.com/docs/13.x/eloquent-factories

A whole library, or a yet another ad for Python, sorry? Why not marvelous Perl, or any lovely PHP’s or a JavaScript faker?
Why a library in the first place?

In case of PHP (checked in v8.1)

echo date('Y-m-d', rand(strtotime('-90 years'), strtotime('-18 years')));
// 2007-07-30

And, I had a snippet for JavaScript (tested in the current Chrome’s EcmaScript).
We get the years in milliseconds, and substract from the current time.

console.log(new Date(Date.now() - 365*24*60*60*1000 * (18 + Math.random()*72)).toISOString().slice(0, 10));
// 1984-07-20

In shell even! Let’s use the common suit GNU coreutils (e.g. v9.4).
We have 90y - 18y = 72 years, that is 26,280 days or ~26,297 days (source)

$ date -d "-18 years -$(( RANDOM % 26297 )) days" -- '+%F';
# 1976-04-06

“You shouldn’t have to choose between open and secure.” The implementation backs that up. The friction is one-time for power users, but it’s a genuine obstacle for scammers and it makes opportunistic spyware installation meaningfully harder.

Source

-–

His argument: power users absorb a one-time inconvenience while vulnerable people (scam victims, children) get protected…
The pattern HN picked up immediately…

That’s the true believer pattern. The argument is ideological, so persuasion is off the table. He read the laws, decided compliance was the correct response, and went to work. Every objection the community raised went nowhere: that this enables surveillance infrastructure, that lying is trivially easy, that the laws themselves are unconstitutional overreach. He’d already accepted the law as legitimate and moved to implementation…

He hit three separate projects in one week…
He agreed entirely, writing that the approach would be “completely ineffective at preventing anyone from lying about their age.” He called it “hilariously pointless.” Then he said Arch Linux should implement it anyway because the law requires it…

The open source community has always relied on the assumption that contributors act in good faith toward user freedom. Taylor probably believes he does. The laws say collect birth dates, so he collected birth dates, and in his framing that was being helpful.

The reason to name him is the pattern. The surveillance state runs on volunteers: people who do the implementation work for free, out of genuine conviction, with no paper trail connecting them to the money that wrote the laws…

Taylor already has the resume line and knows the codebase well enough to try again. The deadline pressure only grows, the laws are real, and someone will be next. The community needs to recognize the pattern before the PR opens, not after.

Source

He said the game is mostly a simulation, but there are also “Easter egg components.”…

To make something like this, he said he first needed the physics of the event itself to model the landslide and the wave it generated. That information came from a paper nearly 20 people from the science community co-authored, including Lynett.

“You can’t do that with AI. You can’t do that with graphic artistry. You have to do that with modeling them the way we did when we create tsunami inundation zones. It’s the same models that we use. It’s engineering level. It’s design level physics,” he said.

From there, he said graphics artistry is needed. And then all of the scene components can be brought together to make the game playable.

Source [web-archive]

Thank you… heartfelt…

Freaking awesome! I adore PHP! <3