Bitwarden NPM Package Hit in Supply Chain Attack

The malware attempts to exfiltrate the collected data via HTTPS but switches to GitHub paths if that fails.“The most notable aspect of this package is that it combines a supply chain compromise of a legitimate CLI identity with a broad post-install secret theft framework. Instead of stopping at .npmrc or a single PAT, the malware systematically pivots across local credentials, CI secrets, GitHub repositories, and multiple cloud secret stores,” JFrog notes.Bitwarden confirmedthe supply chain hack, but noted that its investigation “found no evidence that end user vault data was accessed or at risk, or that production data or production systems were compromised”.The Checkmarx attackThe Bitwarden CLI compromise is linked to the recent supply chain attack on Checkmarx, which hit the company’s public DockerHub KICS image, public ast-github-action, VS Code extension, and Developer Assist extension.On April 22, Checkmarxconfirmedthe incident, sharing details on the malicious artifacts associated with the attack and urging users to immediately rotate secrets and credentials if they were affected.The malware used in the attack was designed to harvest credentials and exfiltrate them to the checkmarx[.]cx domain, or to repositories created under the victim’s GitHub account, a pattern used in the Bitwarden supply chain attack as well.Socket’s analysisof the two incidents also revealed the use of the same embedded payload structure, credential harvesting method, propagation technique, and Russian locale kill switch.“The shared tooling strongly suggests a connection to the same malware ecosystem, but the operational signatures differ in ways that complicate attribution,” Socket notes.The TeamPCP and Shai-Hulud connectionsThe complication, the cybersecurity firm explains, comes from the fact that the Checkmarx attack was claimed by TeamPCP, while the Bitwarden incident references the Shai-Hulud worm that crawled through NPM last year.Also known as DeadCatx3, PCPcat, and ShellForce, TeamPCP is a hacking group active since at least 2024 that has been focusing on supply chain attacks for the past year.The hacking group made headlines over the past month after it compromised Aqua Security’s Trivy vulnerability scanner to steal secrets andpivot across the OSS ecosystemandbeyond.As Socketnotes, TeamPCP apparently claimed responsibility for the Checkmarx incident on social media, which did not come as a surprise, as it had hit the company’s GitHub Actions and OpenVSX plugins as part of the March campaign.However, the Bitwarden payload contains the “Shai-Hulud: The Third Coming” string, suggesting that the incident represents the latest phase of the previous campaign,OX Securitysays.Terms such asatreides, fremen, sandworm,andsardaukarwere also found in the code, which points to a possible overlap with the Shai-Hulud campaigns, but it does not definitely link TeamPCP to the previous attacks, JFrog notes.Shai-Hulud first emerged in the NPM registry in September, when it spread to more than180 packagesusing stolen developer credentials. During a second wave in November, it infectedover 640 packages.“User data is being publicly exfiltrated to GitHub, often going undetected because security tools typically don’t flag data being sent there. This makes the risk significantly more dangerous: anyone searching GitHub can potentially find and access those credentials. At that point, sensitive data is no longer in the hands of a single threat actor; it’s exposed to anyone,” said OX Security team lead Moshe Ben Siman Tov.Related:Are SBOMs Failing? Supply Chain Attacks Rise as Security Teams Struggle With SBOM DataRelated:‘By Design’ Flaw in MCP Could Enable Widespread AI Supply Chain AttacksRelated:OpenAI Impacted by North Korea-Linked Axios Supply Chain HackRelated:European Commission Confirms Data Breach Linked to Trivy Supply Chain Attack

“The most notable aspect of this package is that it combines a supply chain compromise of a legitimate CLI identity with a broad post-install secret theft framework. Instead of stopping at .npmrc or a single PAT, the malware systematically pivots across local credentials, CI secrets, GitHub repositories, and multiple cloud secret stores,” JFrog notes.Bitwarden confirmedthe supply chain hack, but noted that its investigation “found no evidence that end user vault data was accessed or at risk, or that production data or production systems were compromised”.The Checkmarx attackThe Bitwarden CLI compromise is linked to the recent supply chain attack on Checkmarx, which hit the company’s public DockerHub KICS image, public ast-github-action, VS Code extension, and Developer Assist extension.On April 22, Checkmarxconfirmedthe incident, sharing details on the malicious artifacts associated with the attack and urging users to immediately rotate secrets and credentials if they were affected.The malware used in the attack was designed to harvest credentials and exfiltrate them to the checkmarx[.]cx domain, or to repositories created under the victim’s GitHub account, a pattern used in the Bitwarden supply chain attack as well.Socket’s analysisof the two incidents also revealed the use of the same embedded payload structure, credential harvesting method, propagation technique, and Russian locale kill switch.“The shared tooling strongly suggests a connection to the same malware ecosystem, but the operational signatures differ in ways that complicate attribution,” Socket notes.The TeamPCP and Shai-Hulud connectionsThe complication, the cybersecurity firm explains, comes from the fact that the Checkmarx attack was claimed by TeamPCP, while the Bitwarden incident references the Shai-Hulud worm that crawled through NPM last year.Also known as DeadCatx3, PCPcat, and ShellForce, TeamPCP is a hacking group active since at least 2024 that has been focusing on supply chain attacks for the past year.The hacking group made headlines over the past month after it compromised Aqua Security’s Trivy vulnerability scanner to steal secrets andpivot across the OSS ecosystemandbeyond.As Socketnotes, TeamPCP apparently claimed responsibility for the Checkmarx incident on social media, which did not come as a surprise, as it had hit the company’s GitHub Actions and OpenVSX plugins as part of the March campaign.However, the Bitwarden payload contains the “Shai-Hulud: The Third Coming” string, suggesting that the incident represents the latest phase of the previous campaign,OX Securitysays.Terms such asatreides, fremen, sandworm,andsardaukarwere also found in the code, which points to a possible overlap with the Shai-Hulud campaigns, but it does not definitely link TeamPCP to the previous attacks, JFrog notes.Shai-Hulud first emerged in the NPM registry in September, when it spread to more than180 packagesusing stolen developer credentials. During a second wave in November, it infectedover 640 packages.“User data is being publicly exfiltrated to GitHub, often going undetected because security tools typically don’t flag data being sent there. This makes the risk significantly more dangerous: anyone searching GitHub can potentially find and access those credentials. At that point, sensitive data is no longer in the hands of a single threat actor; it’s exposed to anyone,” said OX Security team lead Moshe Ben Siman Tov.Related:Are SBOMs Failing? Supply Chain Attacks Rise as Security Teams Struggle With SBOM DataRelated:‘By Design’ Flaw in MCP Could Enable Widespread AI Supply Chain AttacksRelated:OpenAI Impacted by North Korea-Linked Axios Supply Chain HackRelated:European Commission Confirms Data Breach Linked to Trivy Supply Chain Attack

Bitwarden confirmedthe supply chain hack, but noted that its investigation “found no evidence that end user vault data was accessed or at risk, or that production data or production systems were compromised”.The Checkmarx attackThe Bitwarden CLI compromise is linked to the recent supply chain attack on Checkmarx, which hit the company’s public DockerHub KICS image, public ast-github-action, VS Code extension, and Developer Assist extension.On April 22, Checkmarxconfirmedthe incident, sharing details on the malicious artifacts associated with the attack and urging users to immediately rotate secrets and credentials if they were affected.The malware used in the attack was designed to harvest credentials and exfiltrate them to the checkmarx[.]cx domain, or to repositories created under the victim’s GitHub account, a pattern used in the Bitwarden supply chain attack as well.Socket’s analysisof the two incidents also revealed the use of the same embedded payload structure, credential harvesting method, propagation technique, and Russian locale kill switch.“The shared tooling strongly suggests a connection to the same malware ecosystem, but the operational signatures differ in ways that complicate attribution,” Socket notes.The TeamPCP and Shai-Hulud connectionsThe complication, the cybersecurity firm explains, comes from the fact that the Checkmarx attack was claimed by TeamPCP, while the Bitwarden incident references the Shai-Hulud worm that crawled through NPM last year.Also known as DeadCatx3, PCPcat, and ShellForce, TeamPCP is a hacking group active since at least 2024 that has been focusing on supply chain attacks for the past year.The hacking group made headlines over the past month after it compromised Aqua Security’s Trivy vulnerability scanner to steal secrets andpivot across the OSS ecosystemandbeyond.As Socketnotes, TeamPCP apparently claimed responsibility for the Checkmarx incident on social media, which did not come as a surprise, as it had hit the company’s GitHub Actions and OpenVSX plugins as part of the March campaign.However, the Bitwarden payload contains the “Shai-Hulud: The Third Coming” string, suggesting that the incident represents the latest phase of the previous campaign,OX Securitysays.Terms such asatreides, fremen, sandworm,andsardaukarwere also found in the code, which points to a possible overlap with the Shai-Hulud campaigns, but it does not definitely link TeamPCP to the previous attacks, JFrog notes.Shai-Hulud first emerged in the NPM registry in September, when it spread to more than180 packagesusing stolen developer credentials. During a second wave in November, it infectedover 640 packages.“User data is being publicly exfiltrated to GitHub, often going undetected because security tools typically don’t flag data being sent there. This makes the risk significantly more dangerous: anyone searching GitHub can potentially find and access those credentials. At that point, sensitive data is no longer in the hands of a single threat actor; it’s exposed to anyone,” said OX Security team lead Moshe Ben Siman Tov.Related:Are SBOMs Failing? Supply Chain Attacks Rise as Security Teams Struggle With SBOM DataRelated:‘By Design’ Flaw in MCP Could Enable Widespread AI Supply Chain AttacksRelated:OpenAI Impacted by North Korea-Linked Axios Supply Chain HackRelated:European Commission Confirms Data Breach Linked to Trivy Supply Chain Attack

The Bitwarden CLI compromise is linked to the recent supply chain attack on Checkmarx, which hit the company’s public DockerHub KICS image, public ast-github-action, VS Code extension, and Developer Assist extension.On April 22, Checkmarxconfirmedthe incident, sharing details on the malicious artifacts associated with the attack and urging users to immediately rotate secrets and credentials if they were affected.The malware used in the attack was designed to harvest credentials and exfiltrate them to the checkmarx[.]cx domain, or to repositories created under the victim’s GitHub account, a pattern used in the Bitwarden supply chain attack as well.Socket’s analysisof the two incidents also revealed the use of the same embedded payload structure, credential harvesting method, propagation technique, and Russian locale kill switch.“The shared tooling strongly suggests a connection to the same malware ecosystem, but the operational signatures differ in ways that complicate attribution,” Socket notes.The TeamPCP and Shai-Hulud connectionsThe complication, the cybersecurity firm explains, comes from the fact that the Checkmarx attack was claimed by TeamPCP, while the Bitwarden incident references the Shai-Hulud worm that crawled through NPM last year.Also known as DeadCatx3, PCPcat, and ShellForce, TeamPCP is a hacking group active since at least 2024 that has been focusing on supply chain attacks for the past year.The hacking group made headlines over the past month after it compromised Aqua Security’s Trivy vulnerability scanner to steal secrets andpivot across the OSS ecosystemandbeyond.As Socketnotes, TeamPCP apparently claimed responsibility for the Checkmarx incident on social media, which did not come as a surprise, as it had hit the company’s GitHub Actions and OpenVSX plugins as part of the March campaign.However, the Bitwarden payload contains the “Shai-Hulud: The Third Coming” string, suggesting that the incident represents the latest phase of the previous campaign,OX Securitysays.Terms such asatreides, fremen, sandworm,andsardaukarwere also found in the code, which points to a possible overlap with the Shai-Hulud campaigns, but it does not definitely link TeamPCP to the previous attacks, JFrog notes.Shai-Hulud first emerged in the NPM registry in September, when it spread to more than180 packagesusing stolen developer credentials. During a second wave in November, it infectedover 640 packages.“User data is being publicly exfiltrated to GitHub, often going undetected because security tools typically don’t flag data being sent there. This makes the risk significantly more dangerous: anyone searching GitHub can potentially find and access those credentials. At that point, sensitive data is no longer in the hands of a single threat actor; it’s exposed to anyone,” said OX Security team lead Moshe Ben Siman Tov.Related:Are SBOMs Failing? Supply Chain Attacks Rise as Security Teams Struggle With SBOM DataRelated:‘By Design’ Flaw in MCP Could Enable Widespread AI Supply Chain AttacksRelated:OpenAI Impacted by North Korea-Linked Axios Supply Chain HackRelated:European Commission Confirms Data Breach Linked to Trivy Supply Chain Attack

On April 22, Checkmarxconfirmedthe incident, sharing details on the malicious artifacts associated with the attack and urging users to immediately rotate secrets and credentials if they were affected.The malware used in the attack was designed to harvest credentials and exfiltrate them to the checkmarx[.]cx domain, or to repositories created under the victim’s GitHub account, a pattern used in the Bitwarden supply chain attack as well.Socket’s analysisof the two incidents also revealed the use of the same embedded payload structure, credential harvesting method, propagation technique, and Russian locale kill switch.“The shared tooling strongly suggests a connection to the same malware ecosystem, but the operational signatures differ in ways that complicate attribution,” Socket notes.The TeamPCP and Shai-Hulud connectionsThe complication, the cybersecurity firm explains, comes from the fact that the Checkmarx attack was claimed by TeamPCP, while the Bitwarden incident references the Shai-Hulud worm that crawled through NPM last year.Also known as DeadCatx3, PCPcat, and ShellForce, TeamPCP is a hacking group active since at least 2024 that has been focusing on supply chain attacks for the past year.The hacking group made headlines over the past month after it compromised Aqua Security’s Trivy vulnerability scanner to steal secrets andpivot across the OSS ecosystemandbeyond.As Socketnotes, TeamPCP apparently claimed responsibility for the Checkmarx incident on social media, which did not come as a surprise, as it had hit the company’s GitHub Actions and OpenVSX plugins as part of the March campaign.However, the Bitwarden payload contains the “Shai-Hulud: The Third Coming” string, suggesting that the incident represents the latest phase of the previous campaign,OX Securitysays.Terms such asatreides, fremen, sandworm,andsardaukarwere also found in the code, which points to a possible overlap with the Shai-Hulud campaigns, but it does not definitely link TeamPCP to the previous attacks, JFrog notes.Shai-Hulud first emerged in the NPM registry in September, when it spread to more than180 packagesusing stolen developer credentials. During a second wave in November, it infectedover 640 packages.“User data is being publicly exfiltrated to GitHub, often going undetected because security tools typically don’t flag data being sent there. This makes the risk significantly more dangerous: anyone searching GitHub can potentially find and access those credentials. At that point, sensitive data is no longer in the hands of a single threat actor; it’s exposed to anyone,” said OX Security team lead Moshe Ben Siman Tov.Related:Are SBOMs Failing? Supply Chain Attacks Rise as Security Teams Struggle With SBOM DataRelated:‘By Design’ Flaw in MCP Could Enable Widespread AI Supply Chain AttacksRelated:OpenAI Impacted by North Korea-Linked Axios Supply Chain HackRelated:European Commission Confirms Data Breach Linked to Trivy Supply Chain Attack

The malware used in the attack was designed to harvest credentials and exfiltrate them to the checkmarx[.]cx domain, or to repositories created under the victim’s GitHub account, a pattern used in the Bitwarden supply chain attack as well.Socket’s analysisof the two incidents also revealed the use of the same embedded payload structure, credential harvesting method, propagation technique, and Russian locale kill switch.“The shared tooling strongly suggests a connection to the same malware ecosystem, but the operational signatures differ in ways that complicate attribution,” Socket notes.The TeamPCP and Shai-Hulud connectionsThe complication, the cybersecurity firm explains, comes from the fact that the Checkmarx attack was claimed by TeamPCP, while the Bitwarden incident references the Shai-Hulud worm that crawled through NPM last year.Also known as DeadCatx3, PCPcat, and ShellForce, TeamPCP is a hacking group active since at least 2024 that has been focusing on supply chain attacks for the past year.The hacking group made headlines over the past month after it compromised Aqua Security’s Trivy vulnerability scanner to steal secrets andpivot across the OSS ecosystemandbeyond.As Socketnotes, TeamPCP apparently claimed responsibility for the Checkmarx incident on social media, which did not come as a surprise, as it had hit the company’s GitHub Actions and OpenVSX plugins as part of the March campaign.However, the Bitwarden payload contains the “Shai-Hulud: The Third Coming” string, suggesting that the incident represents the latest phase of the previous campaign,OX Securitysays.Terms such asatreides, fremen, sandworm,andsardaukarwere also found in the code, which points to a possible overlap with the Shai-Hulud campaigns, but it does not definitely link TeamPCP to the previous attacks, JFrog notes.Shai-Hulud first emerged in the NPM registry in September, when it spread to more than180 packagesusing stolen developer credentials. During a second wave in November, it infectedover 640 packages.“User data is being publicly exfiltrated to GitHub, often going undetected because security tools typically don’t flag data being sent there. This makes the risk significantly more dangerous: anyone searching GitHub can potentially find and access those credentials. At that point, sensitive data is no longer in the hands of a single threat actor; it’s exposed to anyone,” said OX Security team lead Moshe Ben Siman Tov.Related:Are SBOMs Failing? Supply Chain Attacks Rise as Security Teams Struggle With SBOM DataRelated:‘By Design’ Flaw in MCP Could Enable Widespread AI Supply Chain AttacksRelated:OpenAI Impacted by North Korea-Linked Axios Supply Chain HackRelated:European Commission Confirms Data Breach Linked to Trivy Supply Chain Attack

Socket’s analysisof the two incidents also revealed the use of the same embedded payload structure, credential harvesting method, propagation technique, and Russian locale kill switch.“The shared tooling strongly suggests a connection to the same malware ecosystem, but the operational signatures differ in ways that complicate attribution,” Socket notes.The TeamPCP and Shai-Hulud connectionsThe complication, the cybersecurity firm explains, comes from the fact that the Checkmarx attack was claimed by TeamPCP, while the Bitwarden incident references the Shai-Hulud worm that crawled through NPM last year.Also known as DeadCatx3, PCPcat, and ShellForce, TeamPCP is a hacking group active since at least 2024 that has been focusing on supply chain attacks for the past year.The hacking group made headlines over the past month after it compromised Aqua Security’s Trivy vulnerability scanner to steal secrets andpivot across the OSS ecosystemandbeyond.As Socketnotes, TeamPCP apparently claimed responsibility for the Checkmarx incident on social media, which did not come as a surprise, as it had hit the company’s GitHub Actions and OpenVSX plugins as part of the March campaign.However, the Bitwarden payload contains the “Shai-Hulud: The Third Coming” string, suggesting that the incident represents the latest phase of the previous campaign,OX Securitysays.Terms such asatreides, fremen, sandworm,andsardaukarwere also found in the code, which points to a possible overlap with the Shai-Hulud campaigns, but it does not definitely link TeamPCP to the previous attacks, JFrog notes.Shai-Hulud first emerged in the NPM registry in September, when it spread to more than180 packagesusing stolen developer credentials. During a second wave in November, it infectedover 640 packages.“User data is being publicly exfiltrated to GitHub, often going undetected because security tools typically don’t flag data being sent there. This makes the risk significantly more dangerous: anyone searching GitHub can potentially find and access those credentials. At that point, sensitive data is no longer in the hands of a single threat actor; it’s exposed to anyone,” said OX Security team lead Moshe Ben Siman Tov.Related:Are SBOMs Failing? Supply Chain Attacks Rise as Security Teams Struggle With SBOM DataRelated:‘By Design’ Flaw in MCP Could Enable Widespread AI Supply Chain AttacksRelated:OpenAI Impacted by North Korea-Linked Axios Supply Chain HackRelated:European Commission Confirms Data Breach Linked to Trivy Supply Chain Attack

“The shared tooling strongly suggests a connection to the same malware ecosystem, but the operational signatures differ in ways that complicate attribution,” Socket notes.The TeamPCP and Shai-Hulud connectionsThe complication, the cybersecurity firm explains, comes from the fact that the Checkmarx attack was claimed by TeamPCP, while the Bitwarden incident references the Shai-Hulud worm that crawled through NPM last year.Also known as DeadCatx3, PCPcat, and ShellForce, TeamPCP is a hacking group active since at least 2024 that has been focusing on supply chain attacks for the past year.The hacking group made headlines over the past month after it compromised Aqua Security’s Trivy vulnerability scanner to steal secrets andpivot across the OSS ecosystemandbeyond.As Socketnotes, TeamPCP apparently claimed responsibility for the Checkmarx incident on social media, which did not come as a surprise, as it had hit the company’s GitHub Actions and OpenVSX plugins as part of the March campaign.However, the Bitwarden payload contains the “Shai-Hulud: The Third Coming” string, suggesting that the incident represents the latest phase of the previous campaign,OX Securitysays.Terms such asatreides, fremen, sandworm,andsardaukarwere also found in the code, which points to a possible overlap with the Shai-Hulud campaigns, but it does not definitely link TeamPCP to the previous attacks, JFrog notes.Shai-Hulud first emerged in the NPM registry in September, when it spread to more than180 packagesusing stolen developer credentials. During a second wave in November, it infectedover 640 packages.“User data is being publicly exfiltrated to GitHub, often going undetected because security tools typically don’t flag data being sent there. This makes the risk significantly more dangerous: anyone searching GitHub can potentially find and access those credentials. At that point, sensitive data is no longer in the hands of a single threat actor; it’s exposed to anyone,” said OX Security team lead Moshe Ben Siman Tov.Related:Are SBOMs Failing? Supply Chain Attacks Rise as Security Teams Struggle With SBOM DataRelated:‘By Design’ Flaw in MCP Could Enable Widespread AI Supply Chain AttacksRelated:OpenAI Impacted by North Korea-Linked Axios Supply Chain HackRelated:European Commission Confirms Data Breach Linked to Trivy Supply Chain Attack

The complication, the cybersecurity firm explains, comes from the fact that the Checkmarx attack was claimed by TeamPCP, while the Bitwarden incident references the Shai-Hulud worm that crawled through NPM last year.Also known as DeadCatx3, PCPcat, and ShellForce, TeamPCP is a hacking group active since at least 2024 that has been focusing on supply chain attacks for the past year.The hacking group made headlines over the past month after it compromised Aqua Security’s Trivy vulnerability scanner to steal secrets andpivot across the OSS ecosystemandbeyond.As Socketnotes, TeamPCP apparently claimed responsibility for the Checkmarx incident on social media, which did not come as a surprise, as it had hit the company’s GitHub Actions and OpenVSX plugins as part of the March campaign.However, the Bitwarden payload contains the “Shai-Hulud: The Third Coming” string, suggesting that the incident represents the latest phase of the previous campaign,OX Securitysays.Terms such asatreides, fremen, sandworm,andsardaukarwere also found in the code, which points to a possible overlap with the Shai-Hulud campaigns, but it does not definitely link TeamPCP to the previous attacks, JFrog notes.Shai-Hulud first emerged in the NPM registry in September, when it spread to more than180 packagesusing stolen developer credentials. During a second wave in November, it infectedover 640 packages.“User data is being publicly exfiltrated to GitHub, often going undetected because security tools typically don’t flag data being sent there. This makes the risk significantly more dangerous: anyone searching GitHub can potentially find and access those credentials. At that point, sensitive data is no longer in the hands of a single threat actor; it’s exposed to anyone,” said OX Security team lead Moshe Ben Siman Tov.Related:Are SBOMs Failing? Supply Chain Attacks Rise as Security Teams Struggle With SBOM DataRelated:‘By Design’ Flaw in MCP Could Enable Widespread AI Supply Chain AttacksRelated:OpenAI Impacted by North Korea-Linked Axios Supply Chain HackRelated:European Commission Confirms Data Breach Linked to Trivy Supply Chain Attack

Also known as DeadCatx3, PCPcat, and ShellForce, TeamPCP is a hacking group active since at least 2024 that has been focusing on supply chain attacks for the past year.The hacking group made headlines over the past month after it compromised Aqua Security’s Trivy vulnerability scanner to steal secrets andpivot across the OSS ecosystemandbeyond.As Socketnotes, TeamPCP apparently claimed responsibility for the Checkmarx incident on social media, which did not come as a surprise, as it had hit the company’s GitHub Actions and OpenVSX plugins as part of the March campaign.However, the Bitwarden payload contains the “Shai-Hulud: The Third Coming” string, suggesting that the incident represents the latest phase of the previous campaign,OX Securitysays.Terms such asatreides, fremen, sandworm,andsardaukarwere also found in the code, which points to a possible overlap with the Shai-Hulud campaigns, but it does not definitely link TeamPCP to the previous attacks, JFrog notes.Shai-Hulud first emerged in the NPM registry in September, when it spread to more than180 packagesusing stolen developer credentials. During a second wave in November, it infectedover 640 packages.“User data is being publicly exfiltrated to GitHub, often going undetected because security tools typically don’t flag data being sent there. This makes the risk significantly more dangerous: anyone searching GitHub can potentially find and access those credentials. At that point, sensitive data is no longer in the hands of a single threat actor; it’s exposed to anyone,” said OX Security team lead Moshe Ben Siman Tov.Related:Are SBOMs Failing? Supply Chain Attacks Rise as Security Teams Struggle With SBOM DataRelated:‘By Design’ Flaw in MCP Could Enable Widespread AI Supply Chain AttacksRelated:OpenAI Impacted by North Korea-Linked Axios Supply Chain HackRelated:European Commission Confirms Data Breach Linked to Trivy Supply Chain Attack

Source: SecurityWeek