A NuGet supply chain attack involving four malicious packages targeting ASP.NET web application developers has been discovered. The campaign deploys a multi-stage payload where NCryptYo acts as a dropper, establishing a local proxy, while companion packages exfiltrate ASP.NET Identity data and accept threat actor-controlled authorization rules, creating backdoors in victim applications. The packages, published between August 12-21, 2024, have accumulated over 4,500 downloads. The attack uses obfuscation, JIT compiler manipulation, and a two-stage architecture to evade detection. The campaign's objective is to compromise applications during development, gaining access to deployed production instances by controlling the authorization layer.
Shai-Hulud 2.0 is a recently identified supply chain attack campaign that demonstrates adaptive techniques to compromise software development pipelines. Although detailed technical specifics are limited, the attack targets the software supply chain, aiming to inject malicious code or backdoors into legitimate software components. This medium-severity threat poses risks to confidentiality, integrity, and availability by potentially distributing compromised software to end users. European organizations relying on affected software or development tools could face increased exposure, especially those in critical infrastructure, finance, and technology sectors. Mitigation requires enhanced supply chain security practices, including rigorous code auditing, dependency verification, and continuous monitoring of software components. Countries with strong software development industries and high dependency on third-party software, such as Germany, France, and the UK, are more likely to be impacted. Given the attack's adaptive nature and supply chain focus, the suggested severity is high, reflecting the potential widespread impact and difficulty in detection. Defenders should prioritize supply chain risk management and incident response readiness to mitigate this evolving threat.
The Shai Hulud npm worm is a supply chain malware attack that has compromised over 26,000 repositories, including high-profile projects such as Zapier, ENS, and Postman. This attack propagates through the npm package ecosystem, leveraging the trust developers place in widely used dependencies. Although no known exploits are actively observed in the wild yet, the scale of affected repositories indicates a significant risk to software supply chains. The worm’s propagation method involves injecting malicious code into npm packages, which then spreads as developers update or install dependencies. European organizations relying on affected npm packages face risks of code integrity compromise, potential data leakage, and disruption of development workflows. Mitigation requires rigorous dependency auditing, use of package integrity verification tools, and restricting automated dependency updates without validation. Countries with strong software development sectors and high npm usage, such as Germany, the UK, France, and the Netherlands, are most likely to be impacted. Given the widespread impact on supply chains and ease of propagation without user interaction, the threat severity is assessed as high. Defenders should prioritize supply chain security measures to prevent infiltration and propagation of such malware in their development environments.
The Shai Hulud npm worm is a supply chain malware infection that compromised approximately 19,000 npm packages, representing a significant threat to the software development ecosystem. This attack propagates through the npm package manager, widely used in JavaScript development, by injecting malicious code into legitimate packages, which then infect downstream projects. Although no known exploits are currently active in the wild, the scale of infection and the nature of supply chain attacks pose a medium-level risk. European organizations relying on npm packages for their software development could face risks including code execution, data exfiltration, or further malware deployment. Mitigation requires thorough auditing of dependencies, use of package integrity verification tools, and restricting automated dependency updates without review. Countries with strong software development sectors and high npm usage, such as Germany, the UK, France, and the Netherlands, are more likely to be impacted. Given the medium severity, the threat demands proactive defensive measures to prevent potential exploitation. Defenders should prioritize supply chain security hygiene and monitor for any emerging exploit activity related to this worm.
A threat actor known as "888" claims to have leaked sensitive LG Electronics data, including source code, configuration files, and hardcoded credentials, via a supply chain compromise through a contractor access point. The leak, currently unconfirmed by LG, could enable attackers to persist within LG systems, conduct lateral movement, and launch sophisticated phishing campaigns using exposed SMTP credentials. Source code exposure may reveal vulnerabilities in LG IoT devices, potentially impacting millions globally. The threat actor has a history of targeting major corporations and monetizing breaches via ransomware or data sales. This incident highlights risks associated with supply chain security and contractor access management. European organizations using LG products or connected to LG supply chains should be vigilant. The severity is assessed as high due to the sensitivity of leaked data and potential for widespread impact.
This threat highlights the risk of AI-assisted software development tools hallucinating non-existent package names, leading to potential supply chain attacks via malicious packages registered by attackers (a form of slopsquatting). An example is the AI suggesting a package 'rails-auth-token' that does not exist, which if blindly trusted and published, could be registered by an attacker with malware. The newly developed open-source tool SlopGuard aims to detect such attacks by verifying package existence, detecting typosquats, and using trust scoring to minimize false positives. While no known exploits are currently in the wild, the threat underscores a growing risk as AI tools become more integrated into development workflows. European organizations relying on package managers like RubyGems, PyPI, and Go modules should be aware of this emerging supply chain risk. Mitigation involves integrating verification tools like SlopGuard into CI/CD pipelines and educating developers on verifying AI suggestions. Countries with strong software development sectors and high adoption of these package ecosystems, such as Germany, the UK, France, and the Netherlands, are most likely to be affected. Given the medium severity rating, the threat poses a moderate risk primarily to software integrity and supply chain trust, with exploitation requiring developer interaction but potentially leading to remote code execution if malicious packages are installed.
A recent campaign has been identified targeting the Visual Studio Code (VSCode) extension marketplace, where attackers have uploaded a dozen malicious extensions aimed at developers. These extensions pose a supply chain attack risk by potentially compromising developer environments and injecting malicious code into software development workflows. Although no known exploits are currently active in the wild, the presence of malicious plugins in a widely used IDE marketplace elevates the risk profile. The threat is assessed as medium severity due to the potential impact on confidentiality and integrity, combined with the ease of exploitation through trusted extension installation. European organizations relying heavily on VSCode for software development could face risks of intellectual property theft, code integrity compromise, and downstream supply chain contamination. Mitigation requires proactive extension vetting, restricting extension installation policies, and monitoring for unusual IDE behaviors. Countries with strong software development sectors and high VSCode adoption, such as Germany, the UK, France, and the Netherlands, are more likely to be affected. Given the medium severity and the supply chain nature of the attack, defenders should prioritize awareness and controls around IDE plugin management.
MCP Snitch highlights a critical security issue with Modern Code Platforms (MCPs) that run with overprivileged tokens, such as GitHub PATs or AWS credentials, without runtime boundaries, enabling potential data exfiltration via prompt injection. Current authentication models lack granular, temporal scoping, forcing broad access tokens that expose entire repositories or cloud resources. MCP Snitch is an open-source proxy tool designed to mediate and restrict MCP operations through whitelist-based access control, runtime permission requests, API key detection, and comprehensive logging. However, it does not address supply chain attacks, persistence mechanisms, or out-of-band operations. This vulnerability underscores the urgent need for sandboxing and protocol-level security primitives in MCPs, akin to the evolution of browser security models. European organizations using MCPs with broad access tokens are at risk of unauthorized data exposure, especially in software development and cloud environments. Mitigations include deploying proxy-based mediation layers like MCP Snitch, enforcing least privilege token scopes where possible, and monitoring MCP activity closely. Countries with significant software development sectors and cloud adoption, such as Germany, France, the UK, and the Netherlands, are most likely affected. The threat severity is assessed as high due to the potential for widespread data compromise, ease of exploitation via prompt injection, and lack of existing granular access controls.
Supply chain attacks have surged by 250% from 2021 to 2024, with third-party vendor compromise accounting for 45% of incidents. These attacks have a longer average dwell time (287 days) compared to direct attacks (207 days), indicating significant detection challenges. The financial impact is substantial, with supply chain attacks costing an average of $5.12 million per incident. CISA has issued an emergency directive emphasizing zero-trust architecture, Software Bill of Materials (SBOM) requirements, and continuous vendor risk assessments to mitigate these threats. European organizations face heightened risks due to their reliance on complex vendor ecosystems and critical infrastructure. Countries with dense technology sectors and critical infrastructure, such as Germany, France, and the UK, are particularly vulnerable. Mitigation requires tailored vendor risk management, adoption of SBOM tools, and enhanced monitoring of supply chain interactions. Given the critical impact on confidentiality, integrity, and availability, ease of exploitation through trusted vendors, and broad scope, this threat is assessed as critical severity.
A self-propagating malware called Shai-Hulud has infected over 500 npm packages, including one with over two million weekly downloads. The worm steals sensitive data, exposes private repositories, and hijacks victim credentials to spread further. It executes when an infected package is installed, collecting system information and GitHub tokens. The malware exfiltrates secrets from repositories, migrates private repositories to public, and self-replicates by infecting the victim's most downloaded packages. Notable infected libraries include those from CrowdStrike. The infection started with ngx-bootstrap version 18.1.4. Prevention measures include using specialized solutions for monitoring open-source components and implementing comprehensive security systems.
Two malicious Python packages, sisaws and secmeasure, were discovered in the Python Package Index (PyPI) repository. These packages, created by the same author, deliver a Remote Access Trojan (RAT) called SilentSync. The RAT is capable of remote command execution, file exfiltration, screen capturing, and web browser data theft. It targets Windows systems and communicates with a command-and-control server using HTTP. The packages employ typosquatting and imitate legitimate modules to deceive users. SilentSync achieves persistence through platform-specific techniques and supports various commands for data exfiltration and system control. This discovery highlights the growing risk of supply chain attacks within public software repositories.
40 npm Packages Compromised in Supply Chain Attack Using bundle.js to Steal Credentials
Source: https://thehackernews.com/2025/09/40-npm-packages-compromised-in-supply.html
A malicious package campaign targeting Python and NPM users on Windows and Linux has been discovered. The attack uses typo-squatting and name-confusion tactics against the popular colorama Python package and the similar colorizr JavaScript package. Multiple packages with risky payloads were uploaded to PyPI, using names similar to legitimate packages in both PyPI and NPM. The unusual tactic of using an NPM package name to attack PyPI users was observed. The payloads allow remote access, control of desktops and servers, and exfiltration of sensitive data. Windows payloads attempt to bypass antivirus protection. The campaign's sophistication suggests targeted adversarial activity, although attribution remains unclear.