Podcast Detail

SANS Stormcast Tuesday, September 8th, 2026: numbat; MicroTik and Magento (Adobe Commerce) 0-Day

If you are not able to play the podcast using the player below: Use this direct link to the audio file: https://traffic.libsyn.com/securitypodcast/10084.mp3

previous
Podcast Logo
numbat; MicroTik and Magento (Adobe Commerce) 0-Day
00:00

My Next Class

Click HERE to learn more about classes Johannes is teaching for SANS

Podcast Transcript

 Hello and welcome to the Tuesday, September 8, 2026
 edition of the SANS Internet Storm Center's Stormcast. My
 name is Johannes Ullrich, recording today from
 Jacksonville, Florida. And this episode is brought to you
 by the SANS.edu Undergraduate Certificate Program in
 Cybersecurity Fundamentals. Well, to start out with, we
 have a diary from Russ about a new tool that Russ discovered,
 Numbat. Numbat was released as open source by Perplexity.
 It's a Go executable, can be downloaded for macOS, Windows
 and Linux. And its main purpose is to monitor what
 your AI agents are up to. So in its simplest form, when you
 start it up, it will enumerate first of all, what AI agents
 are running on a particular system. And then it can log
 what these AI agents are doing. There's also a rule
 language that you can use to further restrict, for example,
 what AI agents are allowed to do or define certain alerts.
 Pretty useful. And Russ is going here through a little
 example where an AI agent runs Nmap. And well, that flags one
 of the rule as the AI agent using a reconnaissance tool.
 Of course, what you consider here a problem or not depends
 on how you're using these AI agents. And the rules are also
 very customizable. So you can adjust them to your own needs.
 But I find just the identifying of the AI agents
 that are running on a particular system, and then
 just logging what they're doing already goes a long way
 to really bring a little bit more accountability to AI
 agents and how they're being used. And late last week or
 this weekend, a new Saturday attack emerged against a micro
 tik routers. A router OS includes, as it turns out, a
 custom SSH daemon. This SSH daemon does not properly
 verify SSH keys. So if you're authenticating with keys,
 you're able to essentially spoof a key and gain access to
 any user's account. This is a pretty odd vulnerability and
 probably, well, you know, one of those reasons that you
 shouldn't code your own crypto. There are sort of
 these two big open source routers, SSH implementations,
 dropbear and openSSH on routers like micro tick
 devices, you often see drop bear, but apparently micro
 tik here went their own way and implemented SSH
 themselves. And that will lead now to this vulnerability
 that's actively being exploited. There is a patch
 available from micro tick as of this weekend. So definitely
 apply it with that patch. You also get some detection
 whether or not your device is already compromised. Micro
 tik implements in the router OS this flagged mechanism. And
 what this refers to is that on boot up MicroTik checks or
 the operating system checks whether or not it was already
 compromised. Of course, it uses sort of some standard
 signatures for that. And if it finds evidence of a
 compromise, it puts the router into the flagged mode, which
 you can then check and basically get used as an alert
 that this device has been compromised. One of the
 commonly noted indicators of compromise for these early
 attacks was the addition of a user account called OPS. OPS.
 So that's also a quick check that you may want to take a
 look at. But of course, that's bound to change. There are no
 public exploits available. So this is only going to get
 worse. And by the time you're listening to this, again,
 assume compromise. But sadly, this is a multi-Saraday
 weekend, not just a long weekend. Style Smuggler is a
 vulnerability that the Sansac has written up on Saturday. It
 affects Magento and Adobe Commerce. This particular
 vulnerability has not been patched yet by Adobe. Now
 there is on Tuesday an upcoming patch Tuesday where
 they may patch it. But this particular vulnerability has
 been exploited at least since Friday, according to Sansac.
 And again, no published patch for this, just some
 workarounds, filters and such that Sansac mentions in their
 blog post. And the noteworthy patch, even though this is not
 yet exploited, the N-Able released the fourth hotfix for
 N-Central. This, I think, the fourth hotfix in a couple
 weeks. And yes, it fixes a critical vulnerability. So
 please get it patched before we have an exploit for this as
 well. N-Central has been a target in the past. So
 definitely something to keep an eye out and also get it
 patched. Well, and this is it for today. So thanks for
 listening. Thanks for liking. Thanks for recommending this
 podcast. And talk to you again tomorrow. Bye.