At the moment, it’s unknown if there was ever a real-world person behind this username or if Jia Tan is a completely fabricated individual.
Well, I’m pretty sure it wasn’t a platypus. There was definitely one or more real-world people behind this. I doubt anyone thinks that their name is actually Jia Tan, though.
The industry has too long neglected the true threat posed to information security by the platypi.
Platypodes
Platypoxen
Platyhaxor
Pl4tyh4x0r
Pretty sure I’ve seen that one on IRC in the 90’s
Platypoodles
I saw someone trying attribute this to Hong Kong based on the possible origins of the name.
Seems like a stretch to me
Failing that hard to not know what is, and isn’t knowable, is a good reason to not give a single f about what they think
It’s crazy how they pressured/manipulated the maintainer. Especially fucked up considering he wasn’t in a good mental state and was still helping the community by maintaining FOSS software.
Specifically, SSH logins were consuming too many CPU cycles and were generating errors with valgrind, a utility for monitoring computer memory.
Through sheer luck and Freund’s careful eye, he eventually discovered the problems were the result of updates that had been made to xz Utils. On Friday, Freund took to the Open Source Security List to disclose the updates were the result of someone intentionally planting a backdoor in the compression software.
It is lucky that Andres Freund checked and found the issue in valgrind that was maybe intentionally or maybe unintentionally.
https://www.openwall.com/lists/oss-security/2024/03/29/4
I’m interested in figuring out what happened and more information on the contributor behind the attack.
Everybody keeps saying it was found by luck, but this seems like it was found by a guy who maintains his repository properly and monitors his CPU cycles diligently just to prevent this sort of thing. I guess I would call it lucky he found it so quickly, but it was definitely not found by luck.
Yep. It could also be found by luck a bit later, or caught in a strict process sooner or later that we won’t know.
No process is perfect, but the fact this attack is super complex, with many levels of indirection on run time, detecting if it’s in debug mode, forcing maintainers to disable Oss fuzzer (a tool that scans source code for bugs and vulnerabilities) and also involved social engineering and took years to get close to widespread release is to show what it takes to plant a back door on 100% Foss systems.
As opposed to closed source, where all it takes is a conversation between govt and a CEO.
to me: the most chilling thing is that someone involved in the open source ecosystem introduced this vulnerability and, if it was intentional, what else did they do?
That’s what I’m most curious about. Was it government? Was it Microsoft, Apple or Google? Was it some lone hacker or group looking for money? Was it just an OSS developer that wanted revenge? It would make for a spicy story.
It isn’t if it was intentional. It was intentional. Otherwise the exploit chain wouldn’t be so convoluted.
