Welcome to The Low Down, the best show on the internet for hackers The Low Down is presented by Maze. LinkedIn: https://www.linkedin.com/company/mazehq/ X: https://twitter.com/Maze_Security Follow Us! https://www.instagram.com/lowdown.pod This week we're diving into viral operating systems under security fire, the GTA 6 leak saga involving insider threats and ransomware, and surveillance technology creeping into your home through radio signals. Today we're talking about: Omaki Linux Vulnerabilities: The Viral OS Under Fire Breaking down the two click RCE vulnerability in Omaki's Chromium extension that exploits YouTube DLP and MPV configuration files. How the attack chain allows malicious configuration files to trigger command execution through video downloads. Why the viral DHH backed Arch based distro is catching security researcher attention and discovering multiple critical vulnerabilities including SSH misconfigurations and Docker daemon privilege escalation. The Bleeding Edge Problem: Why New Operating Systems Are Risky Examining why operating systems are incredibly hard to secure and why convenience features create dangerous attack surfaces. The comparison to AI browsers and why both Chrome and established Linux distros benefit from massive security budgets and talent. Why the Arch User Repository introduces supply chain risks similar to NPM's ecosystem problems. The reality that new code will have vulnerabilities and moving fast means security becomes an afterthought. GTA 6 Leak: Insider Threat, Ransomware, and Shitcoins Rockstar confirms the heartbreaking leak of GTA 6 gameplay footage as legitimate after videos appeared on Cyber Leaks websites. Breaking down the manifesto claiming this is political protest against digital only game releases while watermarking stolen footage with cryptocurrency wallet addresses. Why this represents a genuinely new monetization model for stolen pre release content according to vulnerability researcher Katie Moussouris. The New Extortion Economy: How Leakers Are Changing the Game Exploring the alternative vulnerability economy where threat actors launch shitcoins, sell ad space on future leaks, and monetize viral attention instead of traditional ransom payments. Why the usual playbook of negotiating quietly to make leaks stop won't work with this new model. Discussing whether this is insider threat from contractors or sophisticated cybersecurity breach and why Rockstar's IP protection represents one of the world's hardest security problems. Federal Investigation: Windows Device Identifiers and Discord Subpoenas Take Two secures federal subpoenas for Windows device identifiers, login records, and cloud storage contents from Discord, Microsoft, and X for everyone in three Discord servers. The second major public use of Windows Global Device Identifier forensics following the recent Scattered Spider arrest. Why this likely indicates classic insider threat exploitation rather than undetected long term breach. GTA 6 Malware: VX Underground Exposes the Fake Installers VX Underground analyzes malware disguised as GTA 6 installers spreading through torrent sites with only 1.05 gigabytes suspiciously small file sizes. Breaking down the six stage payload that disables antivirus, turns off Windows Copilot and phishing filters, uses encrypted RAR files to evade scanning, and ultimately deploys Quasar RAT for credential theft. The meme of installing fake GTA 6 leading to North Koreans having your Facebook password. Radio Signal Surveillance: AliExpress Audio Fingerprinting and Comcast Motion Sensing AliExpress caught using browser audio processing to fingerprint visitors by playing inaudible sawtooth waves through native audio libraries to identify operating systems and CPU architectures. Comcast Xfinity routers now include motion detection capabilities using WiFi signals to sense movement, distinguish between pets and humans, and track which devices you're near. Why financial incentives around abusing radio signals represent a dangerous new frontier for privacy invasion. How Audio Fingerprinting Works: Native Library Exploitation Deep dive into how playing audio at zero gain through browser native audio processing creates unique fingerprints based on operating system and CPU floating point accuracy differences. Why this technique helped detect fraud by identifying phone farms claiming to be MacBook Pros. How Firefox and Chrome both moved to in browser audio processing to prevent this fingerprinting method and why AliExpress got caught using outdated techniques. Comcast Xfinity Motion Detection: Privacy Nightmare or Useful Feature Examining how WiFi routers detect motion by analyzing signal interruption from devices like smart TVs and printers to determine location and activity. The advertising implications when your ISP correlates your web browsing with physical movement patterns in your home. Why this enables knowing when to rob
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
If someone approaches you on Discord and says, hello, would you like to download gta6installer.msi.exe.mp4.exe, please don't install it. We don't know anything about this leak. And then you look into it, and it's like, oh, wait, insider threat, ransomware, shitcoin, malware. I was like, oh, damn, okay, yeah. Like, we should actually make a video about this. What is the meme where it's like the giant dominoes, and it's like, me installing GTA 6? North Koreans have my Facebook password. Like that's, that's what this turns into, right?
Good morning, hackers. Welcome to the lowdown, a podcast sponsored by partners over at Maze. Matt, how we doing, man? I don't know if you can see on the camera here. Maybe you're a Spotify listener and you can't see me. I'm a little disheveled right now. My, my wife is out of town for work. And between all these Marchi vulnerabilities and some new ones we're going to talk about here in the podcast, your boy is, your boy is tired, man. How are you doing? Yeah, we got on to record the podcast today and we both just shared the things that we've been like hallucinating through vibe coding because we had a random idea. And I think the phrase that I said was, oh, to have talent and attention deficit disorder, right?
It's just like, oh, every random idea that we come up with, we also now have the capability to like materialize, you know, combination of skill and the tools that are at our disposal now that we could just like speak things into existence. Yeah. Yeah, I have a very bad problem where, like, I can't turn my brain off. I'm constantly thinking about either, like, you know, doing video stuff, like, trying new projects or, like, hanging out with, like, doing family stuff. I'm always in something, making something happen. And the ability for AI to now just, like, exacerbate that problem where, like, you can make anything instantly is, like, not super healthy for me.
But, you know, it is what it is. Yeah, but we're here. We're here. We're doing it. I got myself a new car this week. Ooh. And from the 1900s, it has no computers. Wow. The way I like my cars. Buttons, like physical turn knobs. Oh, yeah. This is how I get my window down. A crank for the windows. Wow. I don't know if you youngins even know what that is. That's crazy. I know. I'm like, I literally was like, I'm excited to toughen my kid up a little bit. I was like, we have one CD player in it.
I get to teach you what a CD is. And we get these 15 songs on this drive. And that is it. I was thinking about that earlier. It's like my son is he's three. And whenever we're in the car, he's like, Daddy, can I have row your boat or like, Daddy, can I have twinkle twinkle or whatever? And like, I'm like, why is he so asking all the time? It's because he knows he can get music on demand. Whereas like when I was a kid, bro, it was the radio that played whatever with no consent. It would just play whatever.
Or it was a CD, you know, that was like start to start to stop. The reason this came up, the reason like it just came up really just before I bought the car, I was actually kind of it was a few days before that, that I was explaining what a CD was to my daughter. Right. It's crazy. I was like, oh, right. I have to explain this. Like, you know, you don't just have these as part of your life. And yes, we just have Spotify in the car. And like you can just yell, you know, Alexa, play poop song. And like I become the number one listener of the poop song on Spotify at the end of the year, whatever it is. Right.
But so I was explaining because we were listening to an album that I like associate with my first car because it was like a CD that just like never left my car. And, you know, like you just didn't bring your whole, like some people had those big binders in their car, but like for me, I, you kind of got stuck with a few CDs that were just in your car for many, many, many weeks or months. Right. At least I did. And so I was listening to one of those CDs. It was cartel chroma, if you know cartel chroma. And it was like in my first car, And so it was just kind of like flashback.
And I was explaining this to her. And she was like, I know what CDs are. I picked them up in Pacopia. They only have one song on them, right? And it's like, there's an item in Pacopia that looks like a CD. And so there we are. So I was like, oh, this is great. I got a Jeep from the 90s. Take the doors off. She gets in it. She goes, this looks like this has been driven a million times. It's kind of rusty. I was like, yeah, that's kind of the point. But I was like, ooh, I'm very excited. No touchscreens. No... No buttons, no nothing. You just get, like, a car. And, yeah, so I'm happy. That's funny.
You know what else is old today? You know what else is super old there, Matt? I think today is the 35th birthday of Linux, potentially. I think I read that somewhere. Either Linux or Ubuntu. It's probably not Ubuntu because Ubuntu is, like, the year is, like, the numbers. I think Linux is 35 years old today. How does it make you feel? That feels both young and old to me at the same time. Like, no, operating systems have always existed. Pre me, of course. Right. Like, and Linux being, you know, the father, the grandmother of all operating systems, the mother root.
Yeah. 1991, according to Linus. There we go. Okay. Well, it has not stopped changing since then as we all have. And what's the hitchhiker's guideline was largely a mistake and made a lot of people really angry. We've created an operating system, which we now realize was a mistake. Yeah. What the heck? You mentioned it in our intro. What is an Omaki, Omaki, Omarchi? What is it?
Yeah, so guys, talking about today, okay, so it's spelled Omarchi Linux. I believe it is correctly pronounced Omaki. I did use Omaki exclusively for one of the Terminal Tower events, so I probably should know how to pronounce it, but alas, here we are. You know, people love... to rice their Linux setups, right? People have to make them look and feel a certain way that they want. The reason being, I think out of the box, a lot of the primarily used Linux distros, like Ubuntu and Arch, like don't come out super useful.
You know, you have to install your editors and then rice your editors, and then, oh, you wanna have like a tiling window manager, and now you have to like configure i3 to be the way that you want. So DHH made Omaki, which like the tagline is Omaki, a beautiful, modern, and opinionated Linux by DHH. It is built on top of Arch Linux. So it's, you know, the word Arch is inside Omaki. The whole point being like it is a distro of Linux that comes out of the box looking pretty. It uses Hyperlan. So you have kind of that window manager that's really kind of fluid and tiled.
And it has, you know, Vim, if you're one of those people. It has a bunch of other tools. Like, I think GIMP by default. It makes it really easy to, like, you put the... His whole shtick is... You want to be able to deploy this ISO to a new box in like under 10 minutes and then just get right to work. It should just work instantly for you. And again, I have used it. It is really fluid and nice. So big fan personally. As you all may know, I actually – I like daily drive Windows. I know heresy in the cybersecurity world, but I also just like all my hardware and networking stacks to work by default.
But, yeah, so the problem with Omaki right now, I think, is, like, they are a very popular, a very fast-moving operating system, or operating system in air quotes, distro of Linux. And so with that come a certain set of vulnerabilities, you know. So we did have a recent CVE. Actually, I'm not even sure if a CVE number got assigned to it by MITRE or otherwise. But basically, it was a two-click RCE in Omaki, specifically because of the setup of how its Chrome is configured.
So again, the issue with a lot of these distros like this, where you have custom Foo installed, is there's kind of this opacity, this lack of transparency to what exactly is inside of it, what is running by default. And as you kind of build... these systems out. If you don't have like clear agreements on what does what you can have maybe conflicting security boundaries. And so this vulnerability in particular is actually what got the Omaki security team created. It was a vulnerability in the Omaki Chromium extension.
that basically if you were tricked into doing a keystroke and then clicked on a notification, so it's a two-click RCE, they would get RCE on your computer, right? The underlying vulnerability is pretty interesting. It actually has to do with, like, the Omarki Chromio extension by default comes with a program called YouTube DLP for downloading and, like, basically ripping videos off YouTube. Very common piece of software. Like, nothing wrong with that being on the computer. But the issue is, within YouTube DLP... You know, when you download the piece of software, or you download the video rather, it may open the video in a video editor, right?
Or a video player. The video player that comes with Omaki is MPV. And MPV is fine, it's fine that it comes with that. But under the hood, MPV takes a configuration file. And inside the configuration file, you are able to run commands before MPV starts. So the full chain is basically, if you can get the browser to think it is downloading a video and then the video gets supplied a basically malicious configuration file in this hex string that comes from the website, if the user tries to download the video,
clicking the notification will trigger RCE ultimately, which is really like, you know, it's not like zero click RCE, auto magic, like get a shell for free type thing. But it is an interesting issue where the security boundaries of the application kind of missed that, oh yeah, this internet data gets pumped to this other application and oh, that other application can use that data to trigger what command gets run ultimately, which is a really neat bug. Yeah, the POC is kind of crazy, right?
And I saw some reactions to it basically saying like Omaki just like straight puts browser notification interactions into Bash as like part of the reason, right? Yeah. I was just kind of like clicking around on this, even just four hours ago from the time that we're recording this, there was a new issue opened up on their GitHub that's like an SSH security issue. We didn't talk about it while we were making the show notes because I just found it. I mean, it's not like a major bone, but basically SSH, when you're setting it up, will like leave password SSH access on kind of no matter what.
So even if you're trying to move to like key only and get rid of password, password stays on. And then also. During setup, the SSH port opens before the key exists. And so the person who wrote this is like the servers enabled, the firewall is open first, and then a bunch of steps after that where the key creation can like fail happen. And then at that point, you're like sitting with an open port with password off and no key. I don't know. So that issue just opened four hours ago.
I haven't like looked too much into it. But this leads me to kind of the broader conversation here, right? Is like we have a viral OS. I feel like an influencer. Come with me to try the viral Linux operating system. Come with me. Based on Arch Linux. Oh, my God, you guys. I've never heard of this. You have to try it. People are lining up around the corner to try this Linux distro. And that's exactly like what's going on. And what comes with that is just so many eyeballs, right? So many eyeballs. And what comes with a ton of eyeballs? Obviously, vulnerabilities.
The other bit is they're very much touting that this is the Vibe Coders operating system. At least what I read about this, it's very much this is built for developers. It's built with agentic workflows in mind. So at least in the branding that I see in my sphere of the internet is the Venn diagram you know, vibe coding and Linux nerds that are trying this is a circle, right? Sure. You know, it seems like that's exactly where they're going.
So not to just, you know, be the AI hater creators that we could be and like just print views all day if we wanted to, like some people are doing. I don't just think like, oh, vibe coding, you know, this on this Linux distro equals bad. This is LOL. This thing is going to be Swiss cheese. No, but like that all being said, Operating systems are hard, man. Like this, this, uh, the, the, the analogy that I think of the, the comparison that I think of to this is the AI browsers, right?
Like we saw this big boom and kind of virality movement around the agentic browsers. And I think we, we might've even talked about it on some of our early episodes. If not, I definitely talked about it on some of my own content. It's like, yeah, Browsers are very hard to get right and get secure. That's why everyone bases their thing off of Chromium is because Google throws a gazillion dollars at the development team to make Chrome Chrome. Chrome has its problems. Chrome has major, major privacy concerns because it's run by an advertising company.
But you cannot say that they don't throw some serious security talent and budget at. Some of the best in the world at browser stuff are working on the Chrome project, right? That cannot be said about random OS that you downloaded today. And the risk profiles are very similar in that this is, not to use your name, this is as low level as you get with stuff that you interact with daily. In your browser, you are giving remote code execution as a service to another person.
Like that's what your web browser is doing. You just need to do it with such guardrails that it can't like completely ruin your life. Same thing with this operating system. And like, I think some of the other bits about this OS that are interesting is like, I've never been an arch user. Take my nerd badge, I know, right? I do drive Linux. You said you daily drive windows. I kind of daily drive all three. Like, at some point I'm touching a Linux box, a Mac box and a Windows box throughout my week, right? I kind of touch everything, but I've never like really enjoyed the Linux on the desktop experience.
I've done it. I've done Ubuntu forever, but I SSH into servers all the time, right? Like Debian stuff and whatnot. But Arch, have you been an Arch user before? No, I used Arch when I was doing Omaki back at the Tower event. In college, I tried to set up a laptop on Arch, and I just found it very clunky and hard to use. And then when it was finally installed and working, you're the one who's beholden to make it look pretty, and I just don't have time for that type of shit, so no. But I feel like culturally or like part of the ethos of this whole ecosystem is it's like an ecosystem, right?
There's like tons of different like packages and stuff to bring in. Yeah, sure. And so this starts to smell a little JavaScript-y, like NPME to me, right, also. So like you're now trusting... almost supply chain level packages as like key parts of your operating system. Well, this is the whole argument about, about like the AUR, right? So what is it? The Arch user repository? Basically it is like a crowd sourced package manager. It's not yum, right? It's or Pac-Man rather.
But it's like the second in command to Pac-Man, and anyone can push anything there. And literally, you're kind of beholden to read it before you install it. I know, a crazy, crazy idea. But yeah, security vulnerabilities, beware when you're talking about Arch. Ultimately, man, I think Omarki is a cool OS. It looks pretty. And the issue is just like, anytime you're going to have... you know, convenience where user data is parsed somewhere with these programs that are going to, like, things are going to go wrong.
It is just inevitable it's going to go wrong, especially if your whole shtick is that you're moving fast, right? Then, you know, security tends to be, like, the last thing that you're worried about, unfortunately. Yeah, I guess, I mean, that's my key point, right? Especially with the browsers, right? When you're taking like a much, much, much smaller development team and pointing them at a tool that is so critical to your security posture and your workflow, like your web browser or your operating system, like we're going to stub our toe. Like these couple of volumes that were like...
pointing at today are just because it's like getting so much attention right now. These aren't the only volumes that exist in this code. I guarantee it. Right. Like, you know, we're just getting eyeballs on it. And they're not the only volumes that are going to exist. Right. They're going to continue to stub their toe. And so I think that's just my takeaway from this. Right. Is like as you try these new browsers, new viral browsers, new viral operating system type things, just know what you're getting into. Right. Not saying like no one should use this, but just like Oh, no, use it for sure. It's just like understand that like it's called the bleeding edge for a reason, right?
Like there's blood. It happens. Yeah. Yeah. Yeah. Just like, I mean, we talked about our last episode, even for like stuff in our home, you just kind of make a decision about your threat model and like what you're willing to do and like what, like what kind of risks you're willing to take on. And I think this is, uh, this is one of those things, new browsers are one of those things like that kind of stuff. So. Yeah, honorable mentions, right, there are two vulnerabilities on top of that. So the whole vulnerability with, like, the two-click to RCE thing kind of kicked off the, hey, RCE should have a security team effort. Since then, the distro has gotten a lot of attention, right, from a security perspective.
So in the last, literally, I think, like, 24 hours, someone dropped a local LPE where, like, the Docker daemon runs as root. So you as a non-root user can kick off a privileged server. Docker image and then mount root to your image and then like overwrite a set UID binary, right? So like not great. And the second one was basically based on, I think the way that Omaki potentially parses and handles one of its USB device descriptors. It runs a binary based on like the name that you plug it in. And so you can exploit that trust boundary, right?
Basically the issue is that you're trusting that a USB device is who it says it is and that is like the core flaw with USB. If you plug in a Raspberry Pi to your Omaki over USB, you can get the Raspberry Pi to advertise that it is this vulnerable USB device. And then from there, pop effectively a root shell. Right. So not great. And again, this is not like anybody in particular's fault. It's just the nature of of code. New code will have vulns. And that's something you got to consider when you're working on a new distro. So, you know, happens, man.
It does. It does. And speaking of risks that you might unnecessarily take. And now I don't know. I literally cannot transition to this one. I might talk about the sponsor transition. No, I was I wasn't going to I was I was going to go to GTA six and I was like trying to think of a GTA. Right. From taking unnecessary risks to like stealing a car and punching the person in the face and multiple cop stars. We're calling out sick on November 26th because the game's coming out. Is that the drop day? It's coming out, man.
It's soon. It's like in two months, three months. Is it a PC thing for you? Is it a console thing for you? I don't know, man. I'm more of a PC gamer now because I like my PC. It's more comfortable in my office chair. But I feel like GTA is one of those games that it's almost culturally required that you're on a PS5 or you're on an Xbox. That's where I played Vice City when I was 12, right? I was on a PS2. Yeah, man. Yeah, I didn't have the date memorized. I also do not have a PS5.
I don't know if this is going to be the reason I buy one. It's probably going to be the reason I like actually get my gaming rig set up at my house. It's been in disarray for a while. Who has time? Who has time? Okay, so I think I've gotten more outreach about this GTA 6 leak than I have anything in the second half of the year of people just like in my DMs being like, are you going to make a video about the GTA 6 leak? And I'm like, we know nothing about the hack or whatever. We don't know. We have no information about what's actually gone on here.
So maybe I should make that video, right? It's just like whatever. But we figured we should talk about it. The quick and dirty. There's someone online that is putting gameplay footage of GTA 6 on a Cyber Leaks website. And they spell it leak like the onion. Cyber Leak. And the gameplay footage come out. Rockstar has been pretty quiet about it. But just this morning, this is why we decided to talk about it. Because Rockstar kind of confirmed that it's real and that they're heartbroken.
And all the work that this is not how they wanted us to see gameplay. So first, after all of this, I can definitely heart goes out to them. I mean, that just sucks, right? But we have no information about how the game was actually stolen or the footage was actually stolen or whatever it is, right? We have like, is this an insider? Is this like some sort of third party? Is this a contractor or was it some sort of cybersecurity incident? We know nothing. My heart goes out to the Rockstar team because you have to consider, like, from just a pure intellectual property management perspective, this is one of the world's hardest problems, right?
You have a game that has likely been in development for a decade or more, and your goal has been, okay, let's make this game, and literally no one can know about it. No one can talk about it ever. You know what I mean? Like people can make millions of dollars off of just extortion if they could do effectively this, right? Yeah. So I think that that's the last word you use there, right? Extortion being kind of the key thing, because otherwise it's like, well, why?
Right. I mean, it's almost it's almost like you're a big target because your particular audience is also the audience that is filled with actual cyber threat actors and talent. I've given a talk the last couple of years at PAX, the video game conference, about kind of the intersection between the video game industry and the cybersecurity industry. Because if you get into like threat actor identification and tracking and all of this, they are in gaming discords, period. Like that is where like every big name hacking group you've read about or read an incident about, they have met each other and organized in gaming communities.
like 100% of the time, like there isn't another example, especially in the Western world. Right. Obviously we know a little bit less about like non-government, like hacking out of like the Eastern world, especially like named groups and all this kind of stuff. But like Western world where like people are getting arrested and we know about them. It's like Roblox, Xbox chats, like Fortnite groups, like Discord stuff, whatever it is. So that I could see, okay, hey, you're highly targeted because you're rock star working on GTA 6.
And it turns out that the threat actor groups are gamers like through and through. But financially, I was like, well, why would they have such a big target on their... Back. And that's what I started. Like we're starting to see this week right now with the GTA six leaks is they under the guise of this is a political protest against rock stars decision to not release physical copies of the game, right? This is going to be a download only game. They're not printing it on discs.
And the manifesto from the threat actor is basically saying, you know, This is BS. Like there's a, there's a big movement around like, Oh, we're now all just like renting everything. We don't, none of us own anything anymore. You know, you don't just like have the game and I get it. Right. I like, I hate it too. I agree. It's terrible. Yeah. Yeah. Yeah. And the constant expansions. And then the real, the real kicker is like their ability to just like turn off your access to something that like you thought you bought. Right. Or like it, it goes away eventually. And that's just kind of weird.
Right. Like I could fire up golden eye on my N64 right now. Right. Like you can't like shut the servers down and take, like take access away of this anyway. So that all being said, that's the manifesto, but yeah, All of the videos that are coming out from this leaker are watermarked with their like crypto wallets addresses. So there's like this financial motive. That's what you can you kind of said extortion that we haven't seen a ton of that like in this world. Obviously, there are examples. The Sony hacks a while ago, you know, whatever.
But there. This isn't like your very common ransomware target, a la healthcare providers or legal providers or stuff like this, right? That have the money and have like the reason to kind of shut it down. But this is like a Katie Masuris, a friend of mine who's just like a legend in the vulnerability research space. Uh, is quoted in this article about the GTA 6 stuff. And she's saying, I'm just going to read her quote directly. This is what the alternative vulnerability economy looks like.
She said the leader launched a cryptocurrency token. Oh, so it's like a, it's a shit coin too, by the way, right? Launched a cryptocurrency token, watermarked stolen footage with a buy link, offered to sell ad space on future leaks because they're going to go viral. Each of those pays out in proportion to how many people are watching. The manifesto is what keeps them watching. This is genuinely a new monetization model for stolen pre-release content, and it means the usual playbook of negotiating a ransom payment quietly or paying to make it stop won't work.
I think this is kind of, okay, now it's worth talking about from a cybersecurity context, no matter how they actually got the leak to begin with. Can I put on my Sinflow hat for a minute? Yes. Yes. I find the timing of all of this very suspicious. What if, hear me out, what if Rockstar is playing seven-dimensional chess and they are the leaguers? What's the benefit? Hype about the game.
You think the GTA 6 was lacking hype? Um, potentially, maybe there's just too much noise in like the games market. Maybe people are mad about the, the Sony no physical disc thing. Maybe this is just them like, you know, 10. I mean, why would a company say no to 10% more profit, right? Like, okay, we make a little noise. We make a fake shit coin. Maybe we have a persona running around that we call the leaker. You think they made the coin too. I think they made it all. Okay, I'm not saying that I think that.
I'm saying just like there is a timeline that could exist where the moon landing was fake, this could also be a thing. You know what I mean? All right, Tucker. Just ask a question. Hey, relax. Just ask a question. I'm not saying that I think they did it, but you got to ask the question. Did Rockstar make their own shit coin and fabricate their own leak? Yeah, I don't think so, but I, okay.
I don't think that this is some grand hack. I'll tell you that. Sure. I think that this is going to be some sort of Occam's razor situation of like a contractor, right? That like, did some crap that they weren't supposed to. Um, that, that all being said, I know some people that have been like high up at like security at these gaming organizations, it's a tight ship because they understand the sensitivity of this, right? I've been in like, I've done some like government stuff. Like I've done some banking stuff, like where you go into a room with multiple badges and eye scans and all this kind of stuff.
And they make sure that stuff can't get out. Right. I've experienced this. So I don't think that Rockstar exactly has zero controls on their contractors. So I'm actually really, really interested in the details because I think they're probably fascinating. I don't think it's like someone walked out with a USB stick or something like that. Can you imagine like, yeah, you know, billion dollar or whatever a year, like, you know, security budget to make sure that like the like their whole. company, all of their profit is derived from a single source of IP that's maybe a terabyte long or a terabyte in size, right?
So protect that at all costs. And then imagine it just gets compromised by a guy walks in, DLP doesn't work, puts in the USB stick, downloads the game, and walks out. Can you imagine, dude? Yeah. I mean, I don't want it to be that because I feel like it has to be more interesting. Right. I agree. I hope. I hope. Yeah. I mean, to your point, right? Like, it comes out in November. Yes. Yes. We're recording this August 26th. To the day it comes out in a few months. Why haven't we seen more marketing or gameplay or footage?
Why does it have to be leaked? I'm shocked that we haven't seen gameplay at this point. The only thing we've seen is there was a gameplay tangential trailer that came out I think a year ago or a year and a half. That's when they dropped the release date. Other than that, we've seen literally nothing. Now, why would you do... Why would you not do this kind of campaign, a PSYOP, if you will, and release gameplay footage? Why would you not do that? If that's the case...
why would you do one exclusively and not both? Right. Yeah. I don't know. Their silence for a few days is a little weird. Like, you know, if this, I don't know. I don't know. Okay. The, the, the other bit worth talking about for us, because it hits on a story that we just talked about a few weeks ago. Did you read about the investigation that they're kicking off the forensics? Like Rockstar into GTA 6? Yeah, so Take-Two is Rockstar's parent company. Right. Okay, I'm not as familiar with that name, but I've heard it, right? They are trying to track this down.
They're like way, I wouldn't even say over, I was about to say overreacting, but they're like, they're having a very strong reaction to this. How about this? Might be an appropriately sized reaction. But Take-Two has now asked for Windows device identifiers login records, and cloud storage contents for every person who spoke in three Discord servers going back to June, is what this says. So the people with the, yeah, there's some other quotes in here about, like, the people doing the investigations of forensics.
But we just talked about this Windows identifier. Yeah. Because it's been, like, all of a sudden it's now, like, this is now the second very public use of this forensic token. Discord has not commented whether or not they are... like responding to this. Well, in this article, so this kind of steps back my it's a conspiracy conversation because federal judges granted the subpoenas against Discord, Microsoft and X, but the petition against Google remains unapproved as of Monday. So they're getting federal courts involved.
So very unlikely that it's a PSYOP now. Okay, tinfoil. Tinfoil. Yeah. So, yeah, Discord hasn't confirmed it, but that they've been served. They just said, we do comply with valid subpoena. So if they got a subpoena, they're complying, right? Yeah. Yeah, the article kind of finishes with my take right is playing out like a classic insider threat exploitation scheme Which is probably most likely right this doesn't this doesn't scream hack that went Unidentified for months, you know to let them exfiltrate all this stuff This screams insider that had access that is trying to cash in on on the situation but
There's some other messery going on. It's part of the reason I wore this T-shirt today. Yeah. Be jealous. This T-shirt sold out very quickly at DEF CON. The homies over at Miscreants, Sean, what up? And they collabed with VX Underground. VX Underground put a thread about this. Apparently, they're getting hit up about the GTA 6 leak a bunch, too. So they looked into it. And there's a ton of malware going on. VX Underground, if you guys don't know, is a malware research group and repository.
They hold a lot of malware samples and they distribute them for researchers and stuff like this. They have analyzed some malware that's going around with the leaks. I mean, obviously this happened, right? So like what are you seeing on that side? Well, before we go underground on this malware, perhaps we go underground on the sponsor of today's podcast, helping you make the world a safer place by checking out to see if your code in your production environment has vulnerabilities. Maze, take it away. Hey hackers, before we keep going, I wanna take a quick break and say a quick thank you to our sponsors. Today's Lowdown episode is sponsored by our friends over at Maze.
Maze has spent the last couple of years using AI to find and remediate vulnerabilities in the cloud. And now they've released Maze Code, AI agents that find and deeply investigate vulnerabilities in your code. Now we all know the deal. Software composition analysis tools and SaaS toolings are all historically really bad at just making more noise. They find issues that may not actually be real and just create a lot of problems for your engineers to deal with that don't solve real security vulnerabilities. I get it. We've been there. Maze code is a really cool tool because Maze code actually knows how your code works.
Maze code investigates every finding with the context of how your code is actually deployed. Sure, you're using a version of libxml2 that's vulnerable, the actual code path to hit that vulnerability is not exposed in your Docker image. MazeCode can find that and won't show you that that vulnerability is a big deal. Every vulnerability that MazeCode reports comes with evidence that it's real and a way to fix it. Check out Maze at go.lowdownpod.com slash Maze. That's go.lowdownpod.com slash Maze. Thanks again, Maze.
Let's keep going. Yeah, so VX Underground doing great work, doing the Lord's work on Twitter. What? What, Matt? What? What? We're just, oh, God, the level of podcast professional we've hit by episode 10 and our ability to throw to the money segment is unparalleled. True. Come at us. Come at us. Anyone else. Yeah. So VX Underground, great guy, does great work. He, quote, unquote, in his own words, likes to bonk goop with a stick, meaning malware, Ari. So, guys, obviously, let me be very clear here.
If someone approaches you on Discord and says, hello, Would you like to download GTA6installer.msi.exe.mp4.exe? Please don't install it, because it is likely one of these goops that are to be bonked with a stick. So, yeah, super interesting stuff, right? So someone on Twitter approached VX Underground and said, Hey, I have the leak supposedly... Would you check it out for me? Because this is getting really popular on like torrenting sites, right? People are peering this file all over the place trying to like push out the leak as far as it will go.
And obviously, bad actors are going to capitalize on that and use kind of the name collision of the real leak and malware to distribute the malware, right? So inside of the GTA 4 setup file, or GTA 6 setup file, rather, which is only 1.05 gigabytes, so just, like, very suspicious to begin with. Like, this game is likely going to be hundreds of gigabytes, just from a pure, like, shaders and texture perspective. Um... Something, something, something. It's a variety of self-packing, self-decompressing, de-encapsulating DLLs that run through multiple layers of de-encapsulation.
Ultimately, at the bottom of the stack is a binary that tries to kill a lot of antiviruses, tries to disable them, like looking for Kaspersky, looking for, you know, ClamAV, looking for a bunch of others. It disables AI, which I guess maybe if you're into that, it's maybe worth running this. It turns off Copilot for you, so that's pretty cool. It turns off phishing filters. It turns off suggestions from Windows. It gets down to a six-stage payload. Stage six uses a... encrypted RAR file so that AV can't scan it, but then has the password, obviously, for the decryption in the payload, unencrypts and then uncompresses the RAR file, and ultimately runs a Quasar RAT, right?
So, like, very common piece of malware that people use for, like, password exfiltration and a bunch of other malicious and various activity, right? So, you know, what is the meme where it's, like, the giant dominoes, and it's, like, me installing GTA VI North Koreans have my Facebook password. Like, that's what this turns into, right? So if you feel like you may have found the crown jewel, like I found the GTA 6 installer, you didn't. I'm pretty confident you didn't. Please, please don't run this. But, yeah, props out to VX Underground. You can follow him on Twitter if you're not, which if you're listening to this, you probably already are.
But, you know, shout out to him. Yeah, man. It's a super weird world out there. Yeah, that, man. Like, yeah. It turns out there's more to talk about than I was giving credit there. I was like, we don't know anything about this leak. And then, like, you look into it, and it's like, oh, wait. Like, insider threat, ransomware, shitcoin, malware. I was like, oh, damn. Okay, yeah. Like, we should actually make a video about this. All right. So this next topic, I... I have my crystal ball for this next topic. Okay. Send it. You have two headlines that are completely unrelated and I'm going to relate them somehow through the power of friendship and magic for everyone.
So this really cool bit of code that someone found on legitimate Ali Express that's using your browser to send out inaudible sounds to actually more accurately fingerprint you, even if you're like, one of these people that tries to avoid being accurately fingerprinted. And then two, and we'll go deeper into each of these two Comcast wifi routers are now motion sensing you through your home for various reasons. Uh, The friendship and magic for everyone unity of these two stories is I feel like we're starting to see some financial incentives behind abusing radio signals that we haven't really seen this before.
We haven't seen a ton of this, like using Wi-Fi signals for motion detecting, using radio signals. your browser to send out audio stuff to fingerprint you. These are quote-unquote legitimate ways to use these pieces of technology. Crystal ball. Crystal ball. If we had a bigger budget, I'd have an animator. Maze? No, I'm kidding. F***. this is going to get abused, right? Like there's no way that these two quote unquote legitimate things, which are kind of BS anyway, right?
Like stop, stop finding new innovative ways to track me, bro. But, but yeah, can you, you, you didn't hear about this AliExpress thing until I told you about it, but you dug in and you said it's super cool. What are they, what are they doing under the hood here? Yeah, so to be very clear, this is AliExpress getting caught using a technique that is now outdated, right? So what this means is they probably left this technique in, but this has been going on for a long time, and we're just now hearing about it, okay? So what's going on here is AliExpress got caught...
fingerprinting visitors using a very particular metric that I knew nothing about. This is a method to fingerprint browsers and ideally to fingerprint not only the browser, but the operating system and the specific CPU that you're on, be it like ARM versus Intel versus AMD versus whatever. Okay. So the way this works is the AliExpress homepage was loading and playing an audio file at zero gain, so you couldn't hear it.
What they were doing was pumping the audio file... through the, at the time, native audio processing libraries of the browser. Okay. So they would play literally just a sawtooth wave and pump it through the audio processing of the browser and then read the output of that audio processing. And by parsing the output, they would get detailed information about specifically not only what browser are you on, but what OS are you on? Because different OSs have different native browser or different native audio processing.
Okay. And then on top of that, potentially, based on differences in the floating point accuracy and the way that this CPU process is already over versus this CPU, information about the CPU that you're on for some form of fingerprinting. Now, I did admittedly pump this through Claude, because I'm like, why do you want to fingerprint browsers? In the world of exploitation, people want to know what browser you're on so they can throw the right V8 exploit at you. But other than that, what does AliExpress have to do with this? And so one good claim that Claude at least called out was like, this could be an anti-fraud thing, right?
When you go to a website, the user agent is your browser telling the server who it is. Hello, I am Chrome. I am Safari. I am Firefox. But obviously that's just an advertisement. That's a claim. That's not actually a proof. Websites want to do their best. to figure out if the claim being made to the UA that you're claiming is actually who you are for a variety of reasons, one being anti-fraud, right? So if you're like a Vietnamese phone farm where you're like a bot factory and you're trying to like scrape AliExpress, it's in AliExpress's interest to know that you are a phone farm, that you're a Samsung Galaxy S8, but you're claiming to be a MacBook Pro, right?
And so by doing this auditory processing, you were at one point able to make that distinction and say, oh, this user is actually on a Samsung phone instead of Chrome on a MacBook like they're claiming. Now, the reason I said that this is an old method that they got caught using is not a current method is because Firefox and Chrome both caught wind of this technique of using the native audio libraries to do fingerprinting, and so now the browsers each have their own independent in-browser audio processing so that you can't do this kind of in-out black box testing.
You probably could still use that library in particular to... fingerprint if you're actually on Chrome or actually on Firefox. But the ability to go low level, it's the name of my channel, by the way, and figure out what OS you're on and maybe what even CPU you're on is no longer a thing. So again, this is a technique that I had no idea existed. It makes sense though, right? If you are able to, from the browser, touch any of the native code and then the native code leaves a fingerprint on the data, especially in the world of like audio processing, it's an easy, cheap way to figure out who you really are, you know? So pretty neat.
Yeah, and then this Comcast one, I mean, it's just like – it just screams abuse to me. Yeah. Right? Where do you think it goes, though? Because, like, what this smells like to me is, like, the ring camera thing, right? It's like ring cameras, right? Back in the day, they were a Shark Tank, you know, startup, whatever. Didn't get Shark Tank funding. Eventually, they got really popular in, like, the early 2010s, and, like, they were super big, right? I think they got acquired by venture capital or PE at some point. And then like we saw the ad during the Super Bowl where it's like, find your lost dog with like the ring botnet.
And everyone's like, oh, it's mass surveillance. Like they're just going to surveil us, which like bad, obvious, terrible use case. What happens with Xfinity, though? Because you can't mass surveil me like eating Cheetos with RF, ideally. You know what I mean? Where does this go? Ideally. So, yeah, I have a few concerns here, namely around like we've seen a lot of this make its way into smart TV land, a lot of like smarter advertising. Like there are cheaper TVs that like have cameras that are pointed at your couch and then like advertising bars on the bottom.
And they're like using data from the camera and like all this sort of stuff to like advertise to you permanently on the TV. And like, look, the TV is cheaper. And it's just like, OK, this sucks. Right. So that's where my head goes on this. Right. Is like if there's any signal of like what kind of person, size person, do you have kids? How many pets? What kind? How many? How many times do you have guests over? And yeah, how granular can this like get right now?
It's saying it can't identify specific people. Um, but if you can identify the size and shape of a, of someone moving around to be like, Oh, don't alert on a pet or a child, which they literally can do by the way. It's on the page. Like don't alert on pets, please. When I'm out of the house. So like, okay, it can pick up size. Right. So, so there is a level of granularity here. Uh, I I'm just saying like, this is going to get, this is going to get worse. It's going to get abused, right? Mostly. And I probably initially by advertisers, um, But then, I mean, we've just seen it over and over again that the privacy chipping away motions by advertisers wind up getting used in threat actors and data brokers and all sorts of other stuff that winds up going on here.
Oh, yeah. Well, I mean, the easy button from like a threat actor perspective is like if I as a hacker can access this about your house, I know when to rob your house. Like, oh, there's been no motion in 10 hours. OK, I'm going to break in and like take whatever I want. From, like, an advertising perspective, it's important to note that not only can they see the weights of things, obviously, based on, like, the don't alert on pets thing. It also says motion detected by the smart TV, motion detected by the Canon printer. They're using, like, the signals of other devices getting interrupted to determine what device you're near.
And so... There is like a dystopian world where it's like, okay, cool. We know when they're on this site for this much time, it tends to keep them on the couch 10% more watching the content. Because it's not only like, they're not just an RF provider, right? They're also your ISP. So they know they're correlating that data against your motion. Like you could sell that for sure. Yeah, I mean, and there's obviously physical activities that you only do in your home that probably would be fingerprintable. You know, like it just just stuff that like, hey, I just don't like more like privacy intruding things.
And this is one of them, no matter how much they wash the PR to like sound like, well, we're just it's just a motion detector. It's like, well, I bought a Wi-Fi router. Why is it motion? detector like you know like this like it's just slippery slope uh on this one um both of these coming out in the same week yeah the browsers kind of stopped that particular fingerprint from working on aliexpress but just like it just got my head going into like radio signals being having dollar signs on them for people and i just don't like the direction that that's going
Yeah, if you're curious how you can get away from this, I guess step one is don't use the router your ISP provides. If you can do anything to make yourself more secure or at least less surveilled, buy a cheap router, flash OpenWRT onto it if you know how to do that. If you don't, buy like... I don't know, like a newer Netgear, a newer Ubiquiti, something like that, and put that in place of your home Wi-Fi router, or your ISPs, rather. If you have to use your ISP, literally, I did this back in my house when I was in Georgia. AT&T required us to use AT&T router, which, by the way, gave them access to my house.
I would literally get notifications when my internet went down. They're like, oh, yeah, we had a hard time getting into your router to do maintenance. And I'm like, I don't like that at all. So what you can do... is put a router behind it in some kind of firewalling where you can basically block all the traffic that the IP address of the outer router has from going into your house, for sure. There's still the question of RF, right? If you're really nitty-gritty, you can take that bitch apart and, like, ground the antennas, right? Or, like, at least put some kind of, like, metal shielding around it so, like, at least the MIMO, the RF protocol, or, I guess, like, spec that they use to do this gets interfered with.
There are ways to get around this. My large complaint is that, like... I always use this analogy in my videos... You know, my grandma is not going to be taking apart her Xfinity router and grounding those antennas. She's going to be playing Mahjong tiles on the computer for fun. Like, that's what she does. You know what I mean? Like, I'm not going to do that, right? Like, you know what I mean? I'm security-minded, and I'm not going to rip the thing open and try to start disabling antennas, right? Like, it's just, like, this is what I'm saying. I just don't want the direction that this is going. You also... This was a story that made the chopping block floor for me, but you mentioned it.
Ubiquiti themselves has just been on a like O-Day patching spree lately, too. I'm a fan of the company, but they've been having a hard time. And just these router manufacturers in general have just such a big target on their back because they're the edge device on a lot of these networks. But, yeah, I mean, it's just rough out there for edge devices. Ubiquiti patched 21 bones today, and the three of them are max CVSS 10s. So, I mean, we don't just, like...
this isn't the CVE list podcast, but since you mentioned it. Yeah, no, for sure. Yeah. Yeah. On that note, update your shit. Put on auto updates, please turn that on. Yeah. Yeah. Hey, man. Speaking of vulnerabilities, bro, we're going to we're going to flash back to the what was that 2020 time period with a big scary bug that may have had a resurgence. Matt, what is log for Jay? Tell me a story. Pop off. Where were you? Where were you when?
Well, Petridge Farm remembers. So Log4J, where do we start? Besides like spurring most cybersecurity vendors marketing for still, like to this day, a lot of people are like, well, this is how we would handle a Log4J incident. It's up there with like solar winds in terms of just like ripple effects of... like, oh, this vulnerability happened or this hack happened and then like the industry changed. Yeah, yeah. Lots of stuff happened in the wake of it. Log4j is one of those, right? So the vulnerability itself was remote code execution.
But the reason that it was like spicy was that A, it was everywhere. And B, it was hard to find. And C, you didn't need a direct line to the internet to be exploitable because it was in the log pipeline. So like if like when Log4j dropped in whatever year of our Lord 20 something, right, that it actually happened. 2021, I want to say it came out and the attackers like M.O.
for that week. And it wasn't just like your normal attackers. Right. It was pretty much anyone because with just a very, very short string, like the exploit string for Log4j was incredibly short. Yeah. And you could just put it anywhere and hope that it would get popped somewhere. And in your exploit string, you just phoned home. And you just then watched your logs for phoning home. And that meant it worked with this couple characters. And then you can go, oh, OK, there's the vulnerability. Now I can go do something spicier than actually just phoning home.
But people put this in user agents. People put this in every get parameter and post parameter and in cookies and whatever, because in the logging, whatever sucked it up, like sucked up parts of the HTTP packet is where the exploit would actually fire. And then on the nightmare side of the blue teamer, that like why it was like a really, really bad couple of weeks for those of us on the defensive side was it. this is a middleware package is what it's called, right?
So like, it turns out that it's like really hard to wind up finding where you have this actually installed and like working. It's not like an open port that you can fingerprint. It's not like something that's easily identified, like, oh, yep, there it is. I'm running that over there. Look, this service is installed, whatever. It was like things that were, it's a thing that's installed in other things. I feel like this is where the industry's new SBOM conversation kind of started, right? SBOM was a thing, obviously, but from a security perspective, not that we didn't care, but we just didn't talk about it as much.
But now it's like, oh, shit, this bug exists, and we literally don't know if we are vulnerable to it because we don't know what's in our code. Even if we knew what code is in our code, we don't know what code is in that code, you know what I mean? Yeah, and it's still a problem, right? We're five, six years later, and that's not solved. It's not like, oh, everyone's inventory is perfect now, right? Like the vendors have made it magically work, right? Like the right combination of cybersecurity vendors have like solved this problem. It's like not actually how it's gone, right?
I've been on the blue team side of this. Many, many, many times, right? Like the, what do we have installed? Where is it on the internet? Does it have a vulnerability? Is it exploitable? Like all these kinds of questions are super, super hard to answer accurately and fast. Right. There are some cool tools like out there that like make this easier in certain situations, but like someone made a joke about this. I tweeted out log4j2 electric bungalow this morning and someone was like, well, at least this time we'll, we know where to find it. Oh, we do? Yeah, my joke was, yeah, because I'm sure we all perfectly maintained our inventories that we created during the incident response five years ago to log4j1.
And that nothing has changed. And we have kept up to speed on all of this. That all being said, I'm not sounding the alarm on this one. Okay. It is a vulnerability in log4j that just dropped, right? There is a POC on GitHub, but it is not, from what we can tell, this is a few hours old. This is not, from what we can tell, as easily exploitable as that first wave. This is scary because... of the vulnerability that it is, remote code execution in this hard to identify platform and generally exploitable without internet access.
That's like the other maiden thing, right? A lot of these vulnerabilities that we talked about, we just talked about routers. Why are routers always catching O days? Because they have to be internet accessible because they are the router, right? In a lot of situations, I'm oversimplifying. But Log4j does not need to be internet accessible to be exploited. But there's some conditions on this one. You looked into it a little bit, right? What's going on? So I guess to set the stage here, the reason why log4j 1.0, like the OG one back in the day was so bad, was any log4j sync that logged data that contained this JNDI markup, right?
This JNDI string, and what that stands for is Java Naming and Directory Interface. would allow that server to call out and pull down another Java class file from anywhere on the Internet. So you put in the string effectively JNDI LDAP, the call home interface, the call home address port number, and a slash in the path. It would go out there. it would pull down that Java class, pull it down, and run it. That was the whole thing.
And it was completely free. So if you were able to push traffic into a network that you could get that string in a place where there was log4j, that was it. That was all the preconditions required. The reason why this one is not necessarily log4j style in the sense of the original one is it has a bunch of preconditions for you to actually be exploited by this. First of all, Your application has to deploy a Java serialized log event receiver. Okay? So this isn't just like a string that lands in a sync. It is you have to have a particular kind of serialized event logger on.
Not only that, but now you also have to have somewhere there is a path that an arbitrary user on the Internet or somewhere you don't trust can push those serialized events into that sync. Okay? You have to be using a vulnerable version of Log4j that has vulnerability, which is not all versions beforehand. I think Log4j 1.0 went back very, very far. This is only to, like, I think 2.16. It's a fairly new bug. It's not, like, as old as the original one was. And then the application that you are pushing your deserialization chain into needs to have other deserialization gadgets that allow you to effectively deserialize into RCE.
And then on top of that, there has to be basically a lack of filtering going on that most applications do have. So the way that the exploit actually works... You are pushing a Java serialized event stream into this filter. The filter will look for only allowable filters or allowable types, right? One of them is like marshalable text, I think, or marshalable events. When it deserializes that, that's the outer layer... Inside of that marshalable event is another object that it did not get filtered through, and then that can be deserialized into, like, a deserialization chain-type attack.
The problem is most applications will push that second stream through a filter, and then ultimately, like, that will get caught by whatever guards are there. So basically a lot of shit has to go wrong for this to be a true vulnerability that you care about, which is much, much different than Log4j 1.0. So, you know, obviously if you are in the world where you're doing Java-based applications and you, you know, look at your S-bomb, see if you have this version of Log4j, upgrade if you do, yada, yada, yada. But it's not the 7 alarm fire that the 2021 version was for sure.
Yeah. Thank God. I mean, obviously, in case we're slightly mistaken on this, if you're if you're hearing this and you haven't at least sniffed this, if you are vulnerable, this is still serious. And there is a chance that you are vulnerable to this. So I would dust off that old S-bomb, make sure that it's up to date. Check the conditions on this and see if you match them, right? But it's not by default, basically, right? So this isn't the, like, Internet is on fire version of this.
Yeah, one good call-out that the article I'm looking at has, we'll put the link in the description of the podcast. If you're a defender who's, like, monitoring network traffic for this type of intrusion, if you're concerned about it, the class you're looking for is a marshaled object. So if you see a lot of, like, marshaled object serialized traffic going on in your network, but it's likely indicative that someone is trying to exploit you with it. Now, if it's successful or not, it's a whole other monitoring and awareness problem. But yeah, that is at least the version of data that the publicly available POC uses right now.
Sweet, sweet. Can I ask you a follow-up to something you mentioned earlier in the episode? Yeah, send it. What is the thing you kept saying you were working on that you used Umaki during? Oh, the Terminal Tower event. Are you aware of that? No. Oh, yeah. So me, oh, God, a bunch of people. Me, the Primogen, Tiege, Bash Bunny, Began, a bunch of others that I'm probably going to miss. S-Fan was there randomly. We had two separate events where we vibe-coded a game. The whole goal was in one week, can we vibe-code a game end-to-end to get it sold on Steam?
Okay. So that was back when the models were like Sonnet three, five Sonnet three, seven. I think we're like the hot models at the time, uh, using cursor sponsored hashtag ad. It was a great time. I love cursor. Um, We did that for a week, and then the second event we did was a follow-up, because we didn't finish the game the first time, because shocker, game dev is hard. The second tower event we did in March of last year, I'm losing track of my years, honestly, but we used Omaki exclusively on that. So the whole setup there was we had BenQ monitors, we had chairs from, I think, either Fractal was the chair manufacturer.
And then Omaki was our OS du jour while we were there. And it was cool, man. It was a good OS. I enjoyed it. The problem is I'm an i3 enjoyer when I'm in my Ubuntu environments, my Debian environments. And all of the keys are different on Omaki, so it was a big learning curve for sure. But it was fun, man. It was a good OS. I keep saying OS. It was a good distro. I enjoyed that distro of Arch for sure. It was fun. That's cool. Did you guys finish the game? No. No. Um, sort of. So, let's see. What the hell is it called? Towers of Mordoria Primogen GitHub?
I'm just, I'm looking it up right now. I'm pretty sure he made it public. Yeah. So this is the current version of the game. It is a real game. So the whole shtick was we were making a... a tower defense that played sort of like Bellatro, right? So it was like Bellatro style and that it was a deck builder and you got these cards and the cards you played to cast a tower and then you would have enemies come down the paths and you would shoot the enemies and upgrade the towers. It played really well. The hard part was like we finished the game at like the last moment of the last day.
It did like almost no balancings. I'm not even sure if the game is winnable in its current state, but but you can play it. It was fun, man. I just found the Prime posted on Reddit. Warning, this game is not fun. Yes, exactly. Mordoria is open source. Warning, this game is not fun. Yeah. Oh, so good, so good. It's like, do not open PRs. I will close them. Oh, yeah, because we had a bunch of people making like, oh, because Prime posted this repo publicly, and then he made a video about people that were doing like PRs where they're like...
doing spelling errors like typos they were fixing them in readmes and saying like commit me please because they want like pr or like uh contributions and so we were getting a bunch of like rogue prs because he made that video the same day he dropped this repo of like you know typo fix this please it was funny so he publicly said hey i'm not gonna close any pr i think i made one actually let's see if it's still there hold on We've got to think of our version of this. What's our... Yes, here it is. My PR, please merge. PR, please merge from low level. That's funny.
We've got to think of our version of this. What can we lock ourselves in a house and hack on live stream for a while? I've thought about this for a long time. What is the Mordoria Tower hacker house version of this? You know what I mean? What can we do that's fun to stream for a week straight? Hacking is like... When it's in a movie, it's neat, but like real life hacking is boring as shit, dude. No, I want to make some. I don't want to I don't want to like necessarily just hack and like find bones like like Bug Bounty Live or whatever.
Like, you know, it exists. It's fun sometimes to watch. Right. Like, but like, what could we make? Right. Like, what could we like make to put out or not finish and make jokes about it after? Speaking of like random live streams, we mentioned it last week and our comments were like into the idea. The DEF CON live stream. I would like everyone to know I am working on it. Like we're trying to identify like the right people, the right talks, all this kind of stuff. And then I will make I will beat. Ed's calendar into submission and pick a day that, and my own calendar into submission. And we'll pick like a Friday that we can just kind of go live and kick it and watch a bunch of Vegas talks and maybe get some of the people to fireside chat.
So heard loud and clear in the comments that you guys were interested in that idea. And I think it'd be really fun. So. We also have some interviews in the pipe with a few people. Those will be fun for sure, getting them scheduled. Calendars are so hard. It turns out people that are really, really interesting to talk to have really busy, crazy lives. I feel like I've been on fire just since DEF CON. Every day it's just been go, go, go, go, go. Yeah, same, same. um looking forward to that day off for gta 6 um let's do that let's do a gaming stream too we've got more ideas than we know what to do with but let's do like a chill thing so that'd be fun for sure all right i think that's it take us out man all right y'all hey seriously thank you for listening i appreciate it we've been loving the podcast how run episode i think this is 10 we're doing this is episode 10 zero index so 11 uh but y'all thanks for watching we really appreciate it we have a really good time with this and maze obviously thank you for helping us get this podcast going and sponsoring us
helping us kick this bad boy off. And we'll see you in the next one. Happy acting, guys. Bye.
Recorded Wednesday, November 18, 2026. Java and NGINX had a bad week. So did anyone trying to catch a flight. The Low Down Podcast is presented by Maze. https://mazehq.com/lowdown X: https://twitter.com/Maze_Security Ed...
Recorded on Friday, November 13, 2026 The Low Down Podcast is presented by Maze. https://mazehq.com/lowdown X: https://twitter.com/Maze_Security 257 A's should not get you into an SSH account. John Hammond joins Ed and...
The Low Down Podcast is presented by Maze. https://mazehq.com/lowdown X: https://twitter.com/Maze_Security The "signup test" was probing for Kubernetes secrets. Ed and Matt get into Railway's AI testing incident, hacked...
Welcome to The Low Down, the best show on the internet for hackers Black October has real bugs, stolen keys, and a lot of very loud headlines. Ed and Matt sort through PHP2Shell, AI security claims, and the difference...
Welcome to The Low Down, the best show on the internet for hackers Listen on Spotify! https://go.lowdownpod.com/spotify The Low Down is presented by Maze. LinkedIn: https://www.linkedin.com/company/mazehq/ X:...