This Week in Security: BugTraq, AI Hacks, and Being Dumb On Planes

After a multi-year hiatus, the venerable BugTraq mailing list is back!

For decades, BugTraq was the place where vulnerabilities were disclosed, from the early days when nearly all vendors viewed all security research as a hostile force, through to the modern era of working with vendors to coordinate disclosing bugs. With the rise of bug bounty programs and other social changes, the mailing list slowly died: what started in 1993 ended in 2021 is returning. The new maintainer, Jonathan Brossard, says in his announcement “The mission is unchanged: full disclosure, researcher-first, no corporate filter.”

Don’t Be Dumb on Planes

In the unlikely event anyone here needs to be told: Don’t do dumb things on planes.

It seems that someone coming home from from the DEF CON hacker conference in Las Vegas decided to mess with the in-plane WiFi, and is likely now in the “find out” phase of doing something dumb. There hasn’t been any public followup beyond the original reports: a passenger on a Delta flight leaving Las Vegas brought up a fake WiFi hotspot named “Delta WiFi FAST” to trick other passengers into connecting, and attempted to disable the in-flight WiFi using a denial of service attack.

The recorded messages from the pilots mention that the legitimate WiFi network was “jammed”, though this is unlikely technically correct. While any radio communications can be jammed by transmitting interference, most WiFi networks are susceptible to several basic denial of service attacks due to oversights in the WiFi standards design; by injecting WiFi management packets that tell the clients that a connection to the access point is no longer valid, and the device will attempt to reconnect.

By spamming the these disconnect packets continually, the network becomes essentially unusable, but unlike jamming, the interference is caused entirely by legitimate packets causing expected behavior. More recent extensions to the WiFi standards mitigate some of the most trivial attacks by adding additional validation that the packets were actually sent by the access point, but very few networks and clients use the newer options.

By rendering the legitimate network useless, the attackers hoped that users would select their fake network instead. None of the reports have included detailed information, but the fake network would likely have prompted the user to enter credentials for another site, such as Google or Facebook. The commercial hotspot model is particularly vulnerable to these sorts of attacks: many hotels, airlines, and businesses run an open, unauthenticated access point, and count on a web page the user must click through to gain access. Users are accustomed to clicking through web pages and providing room or booking numbers, names, or other credentials. Since there is no way to authenticate an open WiFi network, creating a look-alike network can be easy.

In lieu of additional official news, Youtuber [ThioJoe] tracked down some information, or the lack thereof, looking for further clarification; it appears that, contrary to some of the more excited online reports, law enforcement was not present when the plane landed, and it’s unclear if there was even an attempt to kick users from the legitimate WiFi network or a sustained “jamming” or denial-of-service. In an official statement from Delta, they say that no in-flight systems were at risk, which is as it should be: customer-facing WiFi is unlikely to be interfaced with airplane flight systems, and even a true jamming attack generating radio interference would be in the WiFi spectrum where radio noise is already expected.

But we repeat: an airplane is an exquisitely bad location for illegal shenanigans.

Steam Hardware Orders Leaked

The European handler of Steam hardware orders, CEVA, was breached in July, exposing customer order information such as phone numbers, and email addresses.

Steam account details were not compromised, but the order information is plenty to arm scammers with enough information to make a convincing phishing attempt. Valve is already explicitly warning impacted customers to expect fake messages pertaining to their orders.

No additional information has been available on how the attack compromised CEVA. It appears this only impacts Steam hardware preorders in Europe.

Zoom Exploit

Zoom, the meeting software, has patched three serious vulnerabilities that would allow members of a call to execute arbitrary code on other members of the call.

CVE-2026-53413 looks to be a typical buffer overflow, where the length of incoming data is not checked properly and overruns the memory space available for it, crashing the Zoom client or potentially allowing code to be executed. CVE-2026-53414 is a closely related buffer size bug, where the buffer allocated is too small for the read operation, crashing the Zoom client. Finally, CVE-2026-53415 is a use-after-free bug, where memory is referenced after it has been released, allowing code execution. The researchers have branded the three vulnerabilities as “Zoomsday”.

The bad news is that Zoom is a high-profile target for business compromise. All platforms are affected, so if you’re on Zoom, time to update before the next call!

AI Agent Hacks a Reservation System

The Australian Broadcasting Corporation reports on an OpenClaw agent finding flaws in the booking system of a gym when asked to make a reservation. Details are relatively thin, with no complete transcript of the interaction with the OpenClaw agent, but supposedly the agent found that the easiest way to make a booking in the full class was to explore the API of the booking site, discovering that the reservation API was protected, but the cancellation API was not.

Within minutes the Claude-backed agent had booked a gym appointment and pushed the user to the top of the list by cancelling other customers. When asked to undo its work, the agent contritely stated that the insertion API was protected and it was impossible, and that it should have performed a test run first before removing users from a live web service.

With so few details available it’s difficult to ascertain how accurate the report is. Claude has certainly been caught overstepping bounds recently, and the AI frontier companies seem happy for the press of declaring they accidentally hacked other companies, so it all seems plausible. This does nothing but increase the confusion about legal liability.

Under almost any jurisdiction, deliberately hacking the reservation system of a company to jump the line would be considered illegal, but when an agent does it, nobody seems concerned, including the user who launched the request: per the ABC article, “It’s not the end of the world, so I didn’t beat myself up about it, but it certainly was a warning signal to use it responsibly.”

United States to Authorize Private Companies for Cyber Operations

After brain-draining existing government cyber agencies like CISA, this week the US Government issued a memo authorizing the National Coordination Center, part of the Department of Homeland Security to use private companies to perform cyber security responses on behalf of the United States.

The memo requires companies to obey the US Constitution and federal law, and requires a one million dollar bond for each company, but still represents a massive change in the posture of the US government with regards to cyber security. Previously, cyber incidents and responses would often by handled by CISA, the US Army Cyber Command, or the NSA. Allowing private companies to respond on behalf of the country feels almost like a return to letters of marque authorizing piracy and freebooting in the 1800s.

LiteLLM Supply Chain

Some weeks ago we mentioned the compromise of the open source supply chain vulnerability scanner, Trivy. Infected with a supply chain worm which steals credentials and infects every package and build it can now access, the worm has continued to spread, now compromising LiteLLM which is an AI proxy and gateway package used by thousands of enterprises.

LiteLLM was infected because they utilized Trivy as part of the automated build workflow, and the compromise was not detected. Once the worm had access to the LiteLLM publishing credentials, it pushed new versions of the LiteLLM packages, of course infected with the same credential, authentication token, and cryptocurrency stealing code. Like the NPM node.js based worms, this code triggered using the Python startup hooks, causing it to execute as soon as Python indexed available libraries, even if the infected libraries themselves were never used.

The firm Hudson Rock was able to obtain the archive of dumped credentials and data, saying it was 153 GB of compressed content. Trivy, in turn, was compromised in March of 2026 after a misconfigured GitHub workflow allowed a pull request to extract authentication keys. The keys were not fully disabled, and the attacker returned weeks later to infect over 50 Trivy packages and workflows.

Analyzing the contents of the stolen data, the list of credentials stolen is staggering, including GitHub and GitLab credentials for Boeing, Orange Telecom, Roku, and multiple government agencies and labs, as well as Slack credentials, SSH keys, and cloud computing access. Hudson Rock has created a site to look up domain to see if your company has been impacted.

Supply chain compromises continue to spread and impact thousands of packages, but the final goal clearly isn’t to simply spread between packages. When high profile heavily used packages are compromised, the stolen tokens will be used to breach the affected companies sooner or later. The various package ecosystems are still struggling to find solutions to poisoned packages that don’t break existing automation processes, and until those are solved, we can expect continual hacks like these to succeed.

Hacking Solar Inverters, Part 2

Recently, unauthenticated flaws over radio were discovered in solar inverter systems popular as “patio solar” installs in Europe. this week, SaiFlow details vulnerabilities in the REST API of FIMER inverters.

Inverters convert between DC and AC current, and optionally between DC and DC for hybrid systems. They are a core part of energy systems that interface solar, battery, and power grids. SaiFlow targeted FIMER inverters because, in their own words, “batteries catch fire” if the system goes wrong badly enough. They found that the inverters are made of several interconnected components, but at the heart is an embedded Linux system built with buildroot, a system framework similar to traditional distributions or a framework like OpenWRT. Due to a misconfiguration in the nginx webserver, API requests can be sent with no authentication at all, and one of the endpoints allows direct injection of commands over a proprietary protocol.

The proprietary protocol, Aurora, predates internet connectivity on the devices, and lacks any modern protection or authentication. SaiFlow discovered that Aurora uses a six-digit PIN, which would be simple to brute force if the function to read the PIN from flash weren’t also available, with no authentication. And the PIN is disabled by default.

Since Aurora was designed as an internal low-level protocol for controlling the hardware, it has access to critical safety features and the ability to override them. The most significant finding was the ability to enable feeding power to the grid, even if the grid is detected as being disabled. This could damage the inverter itself as it tries to power the whole neighborhood, but worse, like a generator plugged in incorrectly, it could electrocute repair workers handling the power lines. SaiFlow points out this could be enabled fully remotely through the unauthenticated web interface. Other exposed commands allow writing arbitrary data to flash, corrupting the unit, changing the country standards, generating incorrect power exported to the grid, and control over charge and discharge rates and battery charge control.

Vulnerabilities in infrastructure components can be difficult to fix, and SaiFlow reports they have received no meaningful response from FIMER months after reporting them. Hopefully effective patches can be developed soon.

hackaday.com/2026/08/14/this-w…

This Week in Security: BugTraq, AI Hacks, and Being Dumb On Planes

After a multi-year hiatus, the venerable BugTraq mailing list is back!

For decades, BugTraq was the place where vulnerabilities were disclosed, from the early days when nearly all vendors viewed all security research as a hostile force, through to the modern era of working with vendors to coordinate disclosing bugs. With the rise of bug bounty programs and other social changes, the mailing list slowly died: what started in 1993 ended in 2021 is returning. The new maintainer, Jonathan Brossard, says in his announcement “The mission is unchanged: full disclosure, researcher-first, no corporate filter.”

Don’t Be Dumb on Planes

In the unlikely event anyone here needs to be told: Don’t do dumb things on planes.

It seems that someone coming home from from the DEF CON hacker conference in Las Vegas decided to mess with the in-plane WiFi, and is likely now in the “find out” phase of doing something dumb. There hasn’t been any public followup beyond the original reports: a passenger on a Delta flight leaving Las Vegas brought up a fake WiFi hotspot named “Delta WiFi FAST” to trick other passengers into connecting, and attempted to disable the in-flight WiFi using a denial of service attack.

The recorded messages from the pilots mention that the legitimate WiFi network was “jammed”, though this is unlikely technically correct. While any radio communications can be jammed by transmitting interference, most WiFi networks are susceptible to several basic denial of service attacks due to oversights in the WiFi standards design; by injecting WiFi management packets that tell the clients that a connection to the access point is no longer valid, and the device will attempt to reconnect.

By spamming the these disconnect packets continually, the network becomes essentially unusable, but unlike jamming, the interference is caused entirely by legitimate packets causing expected behavior. More recent extensions to the WiFi standards mitigate some of the most trivial attacks by adding additional validation that the packets were actually sent by the access point, but very few networks and clients use the newer options.

By rendering the legitimate network useless, the attackers hoped that users would select their fake network instead. None of the reports have included detailed information, but the fake network would likely have prompted the user to enter credentials for another site, such as Google or Facebook. The commercial hotspot model is particularly vulnerable to these sorts of attacks: many hotels, airlines, and businesses run an open, unauthenticated access point, and count on a web page the user must click through to gain access. Users are accustomed to clicking through web pages and providing room or booking numbers, names, or other credentials. Since there is no way to authenticate an open WiFi network, creating a look-alike network can be easy.

In lieu of additional official news, Youtuber [ThioJoe] tracked down some information, or the lack thereof, looking for further clarification; it appears that, contrary to some of the more excited online reports, law enforcement was not present when the plane landed, and it’s unclear if there was even an attempt to kick users from the legitimate WiFi network or a sustained “jamming” or denial-of-service. In an official statement from Delta, they say that no in-flight systems were at risk, which is as it should be: customer-facing WiFi is unlikely to be interfaced with airplane flight systems, and even a true jamming attack generating radio interference would be in the WiFi spectrum where radio noise is already expected.

But we repeat: an airplane is an exquisitely bad location for illegal shenanigans.

Steam Hardware Orders Leaked

The European handler of Steam hardware orders, CEVA, was breached in July, exposing customer order information such as phone numbers, and email addresses.

Steam account details were not compromised, but the order information is plenty to arm scammers with enough information to make a convincing phishing attempt. Valve is already explicitly warning impacted customers to expect fake messages pertaining to their orders.

No additional information has been available on how the attack compromised CEVA. It appears this only impacts Steam hardware preorders in Europe.

Zoom Exploit

Zoom, the meeting software, has patched three serious vulnerabilities that would allow members of a call to execute arbitrary code on other members of the call.

CVE-2026-53413 looks to be a typical buffer overflow, where the length of incoming data is not checked properly and overruns the memory space available for it, crashing the Zoom client or potentially allowing code to be executed. CVE-2026-53414 is a closely related buffer size bug, where the buffer allocated is too small for the read operation, crashing the Zoom client. Finally, CVE-2026-53415 is a use-after-free bug, where memory is referenced after it has been released, allowing code execution. The researchers have branded the three vulnerabilities as “Zoomsday”.

The bad news is that Zoom is a high-profile target for business compromise. All platforms are affected, so if you’re on Zoom, time to update before the next call!

AI Agent Hacks a Reservation System

The Australian Broadcasting Corporation reports on an OpenClaw agent finding flaws in the booking system of a gym when asked to make a reservation. Details are relatively thin, with no complete transcript of the interaction with the OpenClaw agent, but supposedly the agent found that the easiest way to make a booking in the full class was to explore the API of the booking site, discovering that the reservation API was protected, but the cancellation API was not.

Within minutes the Claude-backed agent had booked a gym appointment and pushed the user to the top of the list by cancelling other customers. When asked to undo its work, the agent contritely stated that the insertion API was protected and it was impossible, and that it should have performed a test run first before removing users from a live web service.

With so few details available it’s difficult to ascertain how accurate the report is. Claude has certainly been caught overstepping bounds recently, and the AI frontier companies seem happy for the press of declaring they accidentally hacked other companies, so it all seems plausible. This does nothing but increase the confusion about legal liability.

Under almost any jurisdiction, deliberately hacking the reservation system of a company to jump the line would be considered illegal, but when an agent does it, nobody seems concerned, including the user who launched the request: per the ABC article, “It’s not the end of the world, so I didn’t beat myself up about it, but it certainly was a warning signal to use it responsibly.”

United States to Authorize Private Companies for Cyber Operations

After brain-draining existing government cyber agencies like CISA, this week the US Government issued a memo authorizing the National Coordination Center, part of the Department of Homeland Security to use private companies to perform cyber security responses on behalf of the United States.

The memo requires companies to obey the US Constitution and federal law, and requires a one million dollar bond for each company, but still represents a massive change in the posture of the US government with regards to cyber security. Previously, cyber incidents and responses would often by handled by CISA, the US Army Cyber Command, or the NSA. Allowing private companies to respond on behalf of the country feels almost like a return to letters of marque authorizing piracy and freebooting in the 1800s.

LiteLLM Supply Chain

Some weeks ago we mentioned the compromise of the open source supply chain vulnerability scanner, Trivy. Infected with a supply chain worm which steals credentials and infects every package and build it can now access, the worm has continued to spread, now compromising LiteLLM which is an AI proxy and gateway package used by thousands of enterprises.

LiteLLM was infected because they utilized Trivy as part of the automated build workflow, and the compromise was not detected. Once the worm had access to the LiteLLM publishing credentials, it pushed new versions of the LiteLLM packages, of course infected with the same credential, authentication token, and cryptocurrency stealing code. Like the NPM node.js based worms, this code triggered using the Python startup hooks, causing it to execute as soon as Python indexed available libraries, even if the infected libraries themselves were never used.

The firm Hudson Rock was able to obtain the archive of dumped credentials and data, saying it was 153 GB of compressed content. Trivy, in turn, was compromised in March of 2026 after a misconfigured GitHub workflow allowed a pull request to extract authentication keys. The keys were not fully disabled, and the attacker returned weeks later to infect over 50 Trivy packages and workflows.

Analyzing the contents of the stolen data, the list of credentials stolen is staggering, including GitHub and GitLab credentials for Boeing, Orange Telecom, Roku, and multiple government agencies and labs, as well as Slack credentials, SSH keys, and cloud computing access. Hudson Rock has created a site to look up domain to see if your company has been impacted.

Supply chain compromises continue to spread and impact thousands of packages, but the final goal clearly isn’t to simply spread between packages. When high profile heavily used packages are compromised, the stolen tokens will be used to breach the affected companies sooner or later. The various package ecosystems are still struggling to find solutions to poisoned packages that don’t break existing automation processes, and until those are solved, we can expect continual hacks like these to succeed.

Hacking Solar Inverters, Part 2

Recently, unauthenticated flaws over radio were discovered in solar inverter systems popular as “patio solar” installs in Europe. this week, SaiFlow details vulnerabilities in the REST API of FIMER inverters.

Inverters convert between DC and AC current, and optionally between DC and DC for hybrid systems. They are a core part of energy systems that interface solar, battery, and power grids. SaiFlow targeted FIMER inverters because, in their own words, “batteries catch fire” if the system goes wrong badly enough. They found that the inverters are made of several interconnected components, but at the heart is an embedded Linux system built with buildroot, a system framework similar to traditional distributions or a framework like OpenWRT. Due to a misconfiguration in the nginx webserver, API requests can be sent with no authentication at all, and one of the endpoints allows direct injection of commands over a proprietary protocol.

The proprietary protocol, Aurora, predates internet connectivity on the devices, and lacks any modern protection or authentication. SaiFlow discovered that Aurora uses a six-digit PIN, which would be simple to brute force if the function to read the PIN from flash weren’t also available, with no authentication. And the PIN is disabled by default.

Since Aurora was designed as an internal low-level protocol for controlling the hardware, it has access to critical safety features and the ability to override them. The most significant finding was the ability to enable feeding power to the grid, even if the grid is detected as being disabled. This could damage the inverter itself as it tries to power the whole neighborhood, but worse, like a generator plugged in incorrectly, it could electrocute repair workers handling the power lines. SaiFlow points out this could be enabled fully remotely through the unauthenticated web interface. Other exposed commands allow writing arbitrary data to flash, corrupting the unit, changing the country standards, generating incorrect power exported to the grid, and control over charge and discharge rates and battery charge control.

Vulnerabilities in infrastructure components can be difficult to fix, and SaiFlow reports they have received no meaningful response from FIMER months after reporting them. Hopefully effective patches can be developed soon.

hackaday.com/2026/08/14/this-w…

This Week in Security: BugTraq, AI Hacks, and Being Dumb On Planes

After a multi-year hiatus, the venerable BugTraq mailing list is back!

For decades, BugTraq was the place where vulnerabilities were disclosed, from the early days when nearly all vendors viewed all security research as a hostile force, through to the modern era of working with vendors to coordinate disclosing bugs. With the rise of bug bounty programs and other social changes, the mailing list slowly died: what started in 1993 ended in 2021 is returning. The new maintainer, Jonathan Brossard, says in his announcement “The mission is unchanged: full disclosure, researcher-first, no corporate filter.”

Don’t Be Dumb on Planes

In the unlikely event anyone here needs to be told: Don’t do dumb things on planes.

It seems that someone coming home from from the DEF CON hacker conference in Las Vegas decided to mess with the in-plane WiFi, and is likely now in the “find out” phase of doing something dumb. There hasn’t been any public followup beyond the original reports: a passenger on a Delta flight leaving Las Vegas brought up a fake WiFi hotspot named “Delta WiFi FAST” to trick other passengers into connecting, and attempted to disable the in-flight WiFi using a denial of service attack.

The recorded messages from the pilots mention that the legitimate WiFi network was “jammed”, though this is unlikely technically correct. While any radio communications can be jammed by transmitting interference, most WiFi networks are susceptible to several basic denial of service attacks due to oversights in the WiFi standards design; by injecting WiFi management packets that tell the clients that a connection to the access point is no longer valid, and the device will attempt to reconnect.

By spamming the these disconnect packets continually, the network becomes essentially unusable, but unlike jamming, the interference is caused entirely by legitimate packets causing expected behavior. More recent extensions to the WiFi standards mitigate some of the most trivial attacks by adding additional validation that the packets were actually sent by the access point, but very few networks and clients use the newer options.

By rendering the legitimate network useless, the attackers hoped that users would select their fake network instead. None of the reports have included detailed information, but the fake network would likely have prompted the user to enter credentials for another site, such as Google or Facebook. The commercial hotspot model is particularly vulnerable to these sorts of attacks: many hotels, airlines, and businesses run an open, unauthenticated access point, and count on a web page the user must click through to gain access. Users are accustomed to clicking through web pages and providing room or booking numbers, names, or other credentials. Since there is no way to authenticate an open WiFi network, creating a look-alike network can be easy.

In lieu of additional official news, Youtuber [ThioJoe] tracked down some information, or the lack thereof, looking for further clarification; it appears that, contrary to some of the more excited online reports, law enforcement was not present when the plane landed, and it’s unclear if there was even an attempt to kick users from the legitimate WiFi network or a sustained “jamming” or denial-of-service. In an official statement from Delta, they say that no in-flight systems were at risk, which is as it should be: customer-facing WiFi is unlikely to be interfaced with airplane flight systems, and even a true jamming attack generating radio interference would be in the WiFi spectrum where radio noise is already expected.

But we repeat: an airplane is an exquisitely bad location for illegal shenanigans.

Steam Hardware Orders Leaked

The European handler of Steam hardware orders, CEVA, was breached in July, exposing customer order information such as phone numbers, and email addresses.

Steam account details were not compromised, but the order information is plenty to arm scammers with enough information to make a convincing phishing attempt. Valve is already explicitly warning impacted customers to expect fake messages pertaining to their orders.

No additional information has been available on how the attack compromised CEVA. It appears this only impacts Steam hardware preorders in Europe.

Zoom Exploit

Zoom, the meeting software, has patched three serious vulnerabilities that would allow members of a call to execute arbitrary code on other members of the call.

CVE-2026-53413 looks to be a typical buffer overflow, where the length of incoming data is not checked properly and overruns the memory space available for it, crashing the Zoom client or potentially allowing code to be executed. CVE-2026-53414 is a closely related buffer size bug, where the buffer allocated is too small for the read operation, crashing the Zoom client. Finally, CVE-2026-53415 is a use-after-free bug, where memory is referenced after it has been released, allowing code execution. The researchers have branded the three vulnerabilities as “Zoomsday”.

The bad news is that Zoom is a high-profile target for business compromise. All platforms are affected, so if you’re on Zoom, time to update before the next call!

AI Agent Hacks a Reservation System

The Australian Broadcasting Corporation reports on an OpenClaw agent finding flaws in the booking system of a gym when asked to make a reservation. Details are relatively thin, with no complete transcript of the interaction with the OpenClaw agent, but supposedly the agent found that the easiest way to make a booking in the full class was to explore the API of the booking site, discovering that the reservation API was protected, but the cancellation API was not.

Within minutes the Claude-backed agent had booked a gym appointment and pushed the user to the top of the list by cancelling other customers. When asked to undo its work, the agent contritely stated that the insertion API was protected and it was impossible, and that it should have performed a test run first before removing users from a live web service.

With so few details available it’s difficult to ascertain how accurate the report is. Claude has certainly been caught overstepping bounds recently, and the AI frontier companies seem happy for the press of declaring they accidentally hacked other companies, so it all seems plausible. This does nothing but increase the confusion about legal liability.

Under almost any jurisdiction, deliberately hacking the reservation system of a company to jump the line would be considered illegal, but when an agent does it, nobody seems concerned, including the user who launched the request: per the ABC article, “It’s not the end of the world, so I didn’t beat myself up about it, but it certainly was a warning signal to use it responsibly.”

United States to Authorize Private Companies for Cyber Operations

After brain-draining existing government cyber agencies like CISA, this week the US Government issued a memo authorizing the National Coordination Center, part of the Department of Homeland Security to use private companies to perform cyber security responses on behalf of the United States.

The memo requires companies to obey the US Constitution and federal law, and requires a one million dollar bond for each company, but still represents a massive change in the posture of the US government with regards to cyber security. Previously, cyber incidents and responses would often by handled by CISA, the US Army Cyber Command, or the NSA. Allowing private companies to respond on behalf of the country feels almost like a return to letters of marque authorizing piracy and freebooting in the 1800s.

LiteLLM Supply Chain

Some weeks ago we mentioned the compromise of the open source supply chain vulnerability scanner, Trivy. Infected with a supply chain worm which steals credentials and infects every package and build it can now access, the worm has continued to spread, now compromising LiteLLM which is an AI proxy and gateway package used by thousands of enterprises.

LiteLLM was infected because they utilized Trivy as part of the automated build workflow, and the compromise was not detected. Once the worm had access to the LiteLLM publishing credentials, it pushed new versions of the LiteLLM packages, of course infected with the same credential, authentication token, and cryptocurrency stealing code. Like the NPM node.js based worms, this code triggered using the Python startup hooks, causing it to execute as soon as Python indexed available libraries, even if the infected libraries themselves were never used.

The firm Hudson Rock was able to obtain the archive of dumped credentials and data, saying it was 153 GB of compressed content. Trivy, in turn, was compromised in March of 2026 after a misconfigured GitHub workflow allowed a pull request to extract authentication keys. The keys were not fully disabled, and the attacker returned weeks later to infect over 50 Trivy packages and workflows.

Analyzing the contents of the stolen data, the list of credentials stolen is staggering, including GitHub and GitLab credentials for Boeing, Orange Telecom, Roku, and multiple government agencies and labs, as well as Slack credentials, SSH keys, and cloud computing access. Hudson Rock has created a site to look up domain to see if your company has been impacted.

Supply chain compromises continue to spread and impact thousands of packages, but the final goal clearly isn’t to simply spread between packages. When high profile heavily used packages are compromised, the stolen tokens will be used to breach the affected companies sooner or later. The various package ecosystems are still struggling to find solutions to poisoned packages that don’t break existing automation processes, and until those are solved, we can expect continual hacks like these to succeed.

Hacking Solar Inverters, Part 2

Recently, unauthenticated flaws over radio were discovered in solar inverter systems popular as “patio solar” installs in Europe. this week, SaiFlow details vulnerabilities in the REST API of FIMER inverters.

Inverters convert between DC and AC current, and optionally between DC and DC for hybrid systems. They are a core part of energy systems that interface solar, battery, and power grids. SaiFlow targeted FIMER inverters because, in their own words, “batteries catch fire” if the system goes wrong badly enough. They found that the inverters are made of several interconnected components, but at the heart is an embedded Linux system built with buildroot, a system framework similar to traditional distributions or a framework like OpenWRT. Due to a misconfiguration in the nginx webserver, API requests can be sent with no authentication at all, and one of the endpoints allows direct injection of commands over a proprietary protocol.

The proprietary protocol, Aurora, predates internet connectivity on the devices, and lacks any modern protection or authentication. SaiFlow discovered that Aurora uses a six-digit PIN, which would be simple to brute force if the function to read the PIN from flash weren’t also available, with no authentication. And the PIN is disabled by default.

Since Aurora was designed as an internal low-level protocol for controlling the hardware, it has access to critical safety features and the ability to override them. The most significant finding was the ability to enable feeding power to the grid, even if the grid is detected as being disabled. This could damage the inverter itself as it tries to power the whole neighborhood, but worse, like a generator plugged in incorrectly, it could electrocute repair workers handling the power lines. SaiFlow points out this could be enabled fully remotely through the unauthenticated web interface. Other exposed commands allow writing arbitrary data to flash, corrupting the unit, changing the country standards, generating incorrect power exported to the grid, and control over charge and discharge rates and battery charge control.

Vulnerabilities in infrastructure components can be difficult to fix, and SaiFlow reports they have received no meaningful response from FIMER months after reporting them. Hopefully effective patches can be developed soon.

hackaday.com/2026/08/14/this-w…

Apache Struts DoS flaws span CVE-2026-73633, CVE-2026-73634, and CVE-2026-73635, plus two JSON plugin bugs. Upgrade to 7.3.0.

#ApacheStruts #Struts2 #DoS #CVE #JavaWeb #CyberSecurity #InfoSec #Vulnerability

http://securityonline.info/apache-struts-dos-flaws-json-plugin/?utm_source=mastodon&utm_medium=jetpack_social

Apache Struts DoS flaws span CVE-2026-73633, CVE-2026-73634, and CVE-2026-73635, plus two JSON plugin bugs. Upgrade to 7.3.0.

#ApacheStruts #Struts2 #DoS #CVE #JavaWeb #CyberSecurity #InfoSec #Vulnerability

http://securityonline.info/apache-struts-dos-flaws-json-plugin/?utm_source=mastodon&utm_medium=jetpack_social

Apache Struts DoS flaws span CVE-2026-73633, CVE-2026-73634, and CVE-2026-73635, plus two JSON plugin bugs. Upgrade to 7.3.0.

#ApacheStruts #Struts2 #DoS #CVE #JavaWeb #CyberSecurity #InfoSec #Vulnerability

http://securityonline.info/apache-struts-dos-flaws-json-plugin/?utm_source=mastodon&utm_medium=jetpack_social