Podcast Detail

SANS Stormcast Friday, March 27th, 2026: TeamPCP Update; DarkSword vs Patches; LangFlow Exploited

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/9868.mp3

previous
Podcast Logo
TeamPCP Update; DarkSword vs Patches; LangFlow Exploited
00:00

My Next Class

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

Podcast Transcript

 Hello and welcome to the Friday, March 27th, 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 Graduate Certificate Program in
 Industrial Control System Security. Well, you can't get
 quite let go of Team PCP and the supply chain compromise.
 Kenneth Hartman, SANS instructor who also did the
 webcast I mentioned yesterday, published a quick update as
 Diary. One of the important points here is that the
 checkmarks compromise affected all 91 tags. That was not sort
 of noted initially. I mentioned yesterday what
 you're seeing now is just the tip of the iceberg. So always
 suspect under reporting. You must rotate credentials even
 if you just suspect that you had an issue. You may have
 some time as apparently Team PCP is a little bit behind in
 actually using all of the credentials. But you really
 also for future reference, you must get good at rotating
 credentials. If you can't do it sort of weakly just for the
 fun of it, without breaking anything, then you're not good
 at it. So try to get to that point. liteLLM. Well,
 because it was compromised, PyPy actually froze that
 particular repo and it now has been released again. liteLLM
 announced that for now they're not going to release any new
 releases. The latest good one is still out there, so you can
 use it if you want to. But before they're doing any new
 releases, they first want to go over their CI/CD pipeline,
 their release procedures to make sure that something like
 this doesn't happen again, which sounds like a very good
 idea. Then, of course, earlier this week we did have the
 Apple updates and there were some questions, some confusion
 about another sort of Apple related event that has gotten
 a lot of press lately and that's a Darksword. So first
 of all, what's Darksword? Darksword is basically a set
 of exploits being used on websites that if a user with a
 vulnerable Apple device visits one of those websites, they're
 getting infected and the exploits being used in Dark
 Sword, they actually came originally out of a little
 more sort of these government sponsored spyware scenarios.
 Koruna was like the name for that particular campaign back
 in July last year. This is really sort of one example
 where these exploits are trickling down from more
 sophisticated to more widely used malware. But what's
 causing confusion is sort of the overlap of these events of
 Apple releasing updates and Darksword sort of being
 discussed in the press. This week's updates did not fix any
 of the vulnerabilities that were used in Darksword. At
 least that's not sort of what's in the update here.
 Early February, Apple released iOS 26.3 and then early March.
 Remember they released these updates for like the older
 operating systems 18.4, 18.6. Those were the updates that
 fixed some of these vulnerabilities used by Dark
 Sword and Koruna. So as long as you use 26.3, which is the
 February version of iOS, you're good as far as Dark
 Sword is concerned. This week's update, you don't need
 to apply it to be safe from these currently used exploits.
 On the other hand, of course, always a good idea to keep
 your stuff up to date. And who knows that I may be the next
 Darksword around the corner that uses new vulnerabilities
 that were patched this week. So definitely update, but it's
 not like a super emergency where anything that was
 patched this week is sort of already being exploited. And
 in the show notes, I'll add a link to a blog post by Google
 that has a real good timeline how these different exploits
 were patched and how they were used by various attackers. And
 yes, let's go back to AI. We do have a vulnerability that
 was recently being discovered in Langflow. Now, Langflow is
 one of those visual systems allows you to create AI
 pipelines and racks. And yes, it had a number of
 vulnerabilities. That's not the first time that there was
 a vulnerability here. But according to a blog by Sysdig,
 this vulnerability was exploited within 20 hours of
 the patch being released. Not a huge surprise given, you
 know, how frequently Langflow is being used. And also, you
 know, with some of these open source tools, of course, the
 diff is much quicker than a bin diff in some kind of a
 commercial tool. That's also probably not all that popular.
 Get it patched. And if you haven't patched yet, assume
 compromise. And didn't I mention rotating keys and all
 that good stuff? So yes, you definitely get to do that.
 Well, and that's it for today. Thanks for listening. Thanks
 for liking. Thanks for subscribing. Next week, of
 course, I'll be in Orlando at our spring conference. So if
 you run into me, I always have some Internet Storm Center
 stickers with me. And well, talk to you again on Monday.
 Bye. Bye. Bye. Bye. Bye! Bye! Thank you.