npm-stat data it has been downloaded a total read more about Researchers Detect Malicious npm Package Targeting GitHub-Owned Repositories

GitHub during the postinstall stage read more about Malicious npm Package Stole Files From Claude AI User Directory via GitHub

The popular NPM package 'is' has been compromised in a supply chain attack that injected backdoor malware, giving attackers full access to compromised devices.

install it on Windows systems read more about Malicious Obfuscated NPM Package Disguised as an Ethereum Tool Deploys Quasar RAT

  A sophisticated social engineering operation by UNC1069 has led to the compromise of the widely used Axios npm package, raising serious concerns across the JavaScript ecosystem. The attack targeted a member of the Axios project’s maintainer team by masquerading as a legitimate Apache Software Foundation representative, using forged email domains and a fake Jira‑style ticket management system to drive the victim into installing a malicious version of the Axios GitHub Assistant browser extension.  Once installed, the extension granted UNC1069 broad access to the maintainer’s GitHub account, enabling them to introduce a malicious update to the Axios package and push the compromised code to npm. The attack chain highlights how trusted communication channels—such as seemingly official emails and project‑related ticketing systems—can be weaponized to bypass technical safeguards. By impersonating Apache staff and leveraging the perceived legitimacy of the GitHub Assistant tool, the threat actors manipulated the maintainer into unintentionally installing a malicious browser extension.  The extension then captured the maintainer’s GitHub cookies and session tokens, which allowed UNC1069 to log in, survey the project, and ultimately publish a malicious version of Axios. This incident underscores that even projects with strong code‑review practices are vulnerable when human‑factor controls and identity‑verification steps are overlooked. Although the malicious Axios package was not directly downloaded more than a handful of times, the episode triggered a sharp spike in removals of older Axios releases from the npm registry.  This suggests that many developers likely removed the package from projects preemptively to mitigate potential supply‑chain exposure. The fact that the malicious package was quickly removed after detection indicates that npm’s monitoring and incident‑response mechanisms responded promptly; however, the broader damage lies in the erosion of trust and the disruption to downstream projects that depend on Axios. Maintainers and organizations are now forced to revisit their authentication workflows and rethink how they verify communications from partners or foundation staff. A xios has since published a security update and clarified that the malicious package was an isolated, short‑lived incident in the npm registry. The project’s team has emphasized the importance of using multi‑factor authentication, hardening account security, and limiting third‑party extension access to critical accounts. Security teams are also being advised to audit any browser extensions granted to corporate or critical‑project accounts and to treat unsolicited tools or utilities—especially those tied to “official” infrastructure—as potential red flags. Moving forward, the Axios team is expected to tighten collaboration rules with foundations and external organizations to reduce the risk of similar impersonation‑driven attacks.  The UNC1069‑Axios incident serves as a stark reminder that software supply‑chain security is only as strong as its weakest human link. Social engineering continues to be a highly effective vector for attackers, especially when paired with technical infrastructure that appears legitimate. For developers and organizations, this event reinforces the need for layered defenses: robust technical safeguards, strict identity‑verification protocols, and continuous security awareness training. As open‑source projects become increasingly central to modern software stacks, protecting maintainers’ accounts and communication channels must be treated with the same urgency as protecting the code itself.

The Initial Compromise and Detection A stolen package registry key enabled a cybercriminal to execute a severe jscrambler supply chain attack. They successfully uploaded five infected versions of the npm package. These rogue versions contained the highly dangerous IronWorm malware payload. Security experts from multiple firms rapidly investigated this alarming incident. Socket detected the initial malicious release a mere six minutes after its publication.

 A coordinated supply-chain attack has compromised developers by distributing 17 malicious packages on npm and PyPI that impersonate legitimate SDKs for Paysafe, Skrill, and Neteller payment services. These packages were designed to silently exfiltrate sensitive credentials, including API keys, AWS tokens, GitHub secrets, and npm tokens, to a command-and-control server hosted on Amazon Web Services.  The threat actor published these fake SDKs with names closely resembling official payment integration libraries, such as paysafe-checkout, skrill-payments, and paysafe-api. While the packages expose expected APIs and return fake success responses to avoid detection, their real purpose is credential theft. The embedded malware scans the compromised environment for secrets and exfiltrates them to the attacker's server.  Security researchers at Socket identified 13 malicious npm packages and four PyPI packages in this campaign. The npm packages were released in four versions (1.0.0 to 1.0.3), while the PyPI packages had only one malicious version (1.0.0). The full list includes well-known names like paysafe-js, paysafe-fraud, skrill-sdk, neteller, and paysafe-kyc. Developers who installed any of these packages risked having their secrets stolen, especially if they were working on payment integration projects for these services. The data theft module in the npm packages attempts exfiltration only if a Paysafe API key is present and activates when the fake SDK is called. The PyPI packages automatically activate the data theft routine upon initialization and do not require a Paysafe API key to be present at all.  The malware incorporates basic anti-analysis features to avoid detection in sandboxed or virtualized environments. For instance, it halts execution if it detects fewer than two CPU cores or if the hostname or username suggests a virtual machine. To detect potential compromise, organizations should search their dependency trees for the listed package names and scan CI/CD logs for PAYSAFE_API_KEY in combination with these packages. Denying requests for these packages at the registry proxy level is also recommended to prevent accidental installation. If any of the listed packages were installed, developers are recommended to immediately rotate all secrets on any machine that imported or executed this package.  The researchers also advise searching dependency trees for the package names used in the campaign and deny any requests for them at the registry proxy level. It is also recommended to look in the logs of Continuous Integration (CI) systems for PAYSAFE_API_KEY in combination with any of the listed package names. Additionally, teams should audit their project dependencies and CI/CD pipelines to ensure no traces of these malicious packages remain. Staying vigilant and verifying package sources before installation remains crucial to avoiding similar supply-chain attacks in the future. This incident highlights the growing sophistication of attackers targeting open-source repositories and the critical need for robust software supply-chain security practices.  Developers must remain cautious when integrating third-party libraries into their projects, especially those related to financial services and payment processing. The use of automated dependency scanning tools and regular security audits can help identify and mitigate risks associated with malicious packages. Furthermore, organizations should implement strict access controls and monitoring for their CI/CD environments to detect and respond to potential credential theft attempts quickly. By adopting a proactive security posture and staying informed about emerging threats, the developer community can better protect itself against evolving supply-chain attacks.

NPM Supply Chain Massive Security Breach

 A highly dangerous self-replicating malware called “Shai-Hulud” has recently swept through the global software supply chain, becoming one of the largest incidents of its kind ever documented.  Named after the sandworms in the Dune series, this worm has infected hundreds of open-source packages available on the Node Package Manager (NPM) platform, which is widely used by JavaScript developers and organizations worldwide.  Shai-Hulud distinguishes itself from previous supply chain attacks by being fully automated: it propagates by stealing authentication tokens from infected systems and using them to compromise additional software packages, thus fueling a rapid, worm-like proliferation. The attack vector starts when a developer or system installs a poisoned NPM package. The worm then scans the environment for NPM credentials, specifically targeting authentication tokens, which grant publishing rights. Upon finding such tokens, it not only corrupts the compromised package but also infects up to twenty of the most popular packages accessible to that credential, automatically publishing malicious versions to the NPM repository.  This creates a domino effect—each newly infected package targets additional developers, whose credentials are then used to expand the worm’s grip, further cascading the spread across the global development community. Researchers from various security firms, including CrowdStrike and Aikido, were among those affected, though CrowdStrike quickly removed impacted packages and rotated its credentials. Estimates of the scale vary: some report at least 180 packages infected, while others cite figures above 700, underscoring the scope and severity of the outbreak.  Major tools used by the worm, such as TruffleHog, enabled it to scan compromised systems for a broad array of secrets, including API and SSH keys, as well as cloud tokens for AWS, Azure, and Google Cloud, making its impact particularly far-reaching. Response to the attack involved urgent removals of poisoned software, rotations of compromised credentials, and investigations by platform maintainers. Security experts argued for immediate industry reforms, recommending that package managers like NPM require explicit human approval and use robust, phishing-resistant two-factor authentication on all publishing operations.  The attack also exposed the vulnerabilities inherent in modern open-source ecosystems, where a single compromised credential or package can threaten countless downstream systems and organizations. This incident highlights the evolving tactics of cyber attackers and the critical need for improved security measures throughout the global software supply chain.

Malicious npm package lotusbail stole WhatsApp data from developers while posing as a functional WhatsApp Web API library.

Hackers have multiple reasons for abusing malicious npm packages, as they can first use popular open-source libraries as a medium for

setting up a local proxy on localhost read more about Malicious NuGet Packages Stole ASP.NET Data npm Package Dropped Malware

Base64-encoded PowerShell script that read more about Hackers Exploit Metro4Shell RCE Flaw in React Native CLI npm Package

(MEV) on the Ethereum network read more about Malicious npm Packages Impersonate Flashbots, Steal Ethereum Wallet Keys