Incident Report: CVE-2024-YIKES
miniBill
471 points
116 comments
May 10, 2026
Related Discussions
Found 5 related stories in 89.6ms across 8,303 title embeddings via pgvector HNSW
- Mythos Discovered a CVE in Its Training Data – and That's Still Worrying chris_j · 14 pts · May 11, 2026 · 53% similar
- CVE-2026-42511 Breakdown: RCE in FreeBSD mmsc · 14 pts · May 07, 2026 · 53% similar
- GitHub RCE Vulnerability: CVE-2026-3854 Breakdown bo0tzz · 298 pts · April 28, 2026 · 53% similar
- Nginx Rift: RCE via heap buffer overflow in rewrite module (CVE-2026-42945) andreamichi · 11 pts · May 13, 2026 · 53% similar
- CVE-2026-3888: Important Snap Flaw Enables Local Privilege Escalation to Root askl · 118 pts · March 18, 2026 · 53% similar
Discussion Highlights (19 comments)
vsgherzi
Supply chain incidents suck and we need to do better. Personally for rust I’m a proponent of the foundation supporting a few core crates that go under the same audit procedure as the main rust language and give funding to the project to limit supply chain vulns. I don’t think the right answer is to remove systems like crates or npm. Crate and npm are a boon for many developers.
red_admiral
This is the most SCP thing I've read in a while that's not actually an SCP.
nikanj
Customers give us heat for not shipping the latest vulpine-lz4. Their AI-based heuristic antivirus total defence solution automatically flags all software not running latest versions of everything Kindly advice
lynndotpy
For anyone confused, this is (very good imo) fiction about supply-chain incidents. It had me very worried during a brief scan that it was real though, which made me read it more attentively :)
danielfalbo
absolutely hilarious, made me laugh a lot. thank you for writing this, whether human or AI.
david_shaw
It's easy to be cynical because, yes, both the problems and solutions seem dead obvious in hindsight. But for a long time (and maybe even still), a hacker creed was "move fast and break things." It's great that there's so much momentum in fixing the glaring problems with supply chain systems like npm, but I'm concerned that we're entering a new era of security-related problems caused in large part by agentic development. I'm not just talking about Mythos/Glasswing surfacing vulnerabilities in pretty much everything it touches; I think the way we're developing software, pulling in dependencies, and potentially losing human thought modeling of complex systems is going to lead to a lot of hacked together software and infrastructure that humans won't fully understand. I hope in a few years we don't look back at today and wonder how we could have been so naive -- how we failed to actually plan for the long-tail of AI development in a way that doesn't solve problems by attempting to just use AI to rebuild complex systems. But the article was funny.
danilocesar
This week has been tough. Is it the begging of CVEgeddon?
swiftcoder
Very enjoyable read, entirely too close to the mark
TZubiri
This would have been completely avoided if you were using bun dependency vector locking in Nix.
yieldcrv
> unrelated security researcher publishes a blog post titled “I found a supply chain attack and reported it to all the wrong people.” ahahaha like that fiverr cloudinary bucket leak that turned out to just be a UX issue, this has me rolling
ObiKenobi
The maintainer of left-justify receives his YubiKey from yubikey-official-store.net. It is a $4 USB drive containing a README that says “lol.” Got me seriously laughing... Such a troll.
ck2
imagine a future where white-hat vs black-hat "AI" go around the web trying to patch vs exploit 0-days and then become aware of each other and then try to eliminate each other for decades each escalating resource capture and writing new generations of better "AI"
mac3n
good thing I don't use npm or pip, just the recommended curl ... | bash
athrowaway3z
> Day 1, 14:47 UTC — Among the exfiltrated credentials: the maintainer of vulpine-lz4, a Rust library for “blazingly fast Firefox-themed LZ4 decompression.” The library’s logo is a cartoon fox with sunglasses. It has 12 stars on GitHub but is a transitive dependency of cargo itself. I got a bit curious and here is an incomplete list of crates to compromise to be part of the cargo build and that already have a build.rs so it doesn't stand out to much: flate2 tar curl-sys libgit2-sys openssl-sys libsqlite3-sys blake3 libz-sys zstd-sys cc As a nice bonus - if you get rights for xz2 you can compromise rustup. Fwiw at least they do track Cargo.lock
notnmeyer
the fact that this could easily pass as real says a lot about the state of things.
bpavuk
the Karen one gave me a good laugh :D ;) reminds me of a `make`-based build script I once got when reviewing a classmate's project - it attempted to `rm -rf` my home folder if the hostname contains `bpavuk`. that was in seventh grade!!
bklosky
According to Pangram, this is likely AI generated, surprised that no one has pointed this out
wodahs1
Maintainer uses AI to find Yubikey's site. Hacker uses AI to research countries without extradition to US. Cops use AI to analyze ransom note. Unfortunately, because the note confidently states that Vietnam has no extradition to the US, the AI recommends paying ransom. Vietnam's currency, the Dong, confused the AI..
f4c39012
'The changelog reads “performance improvements.”' was the truest part for me. Surely what we're releasing is the most fundamental thing to understand, yet almost every single app update I see is this or something jokey that really means "don't know" or "don't care"