FeedExploreAsk AIAlertsSavedProfile

Categories

AICybersecurityInfrastructureDatabaseTech Updates

Tech news that matters.

FeedExploreAskAlertsSavedProfile
Back to feed
Cybersecurity·CriticalBreaking

Malware Hits npm, PyPI, Crates.io

A conceptual image representing a software supply chain attack, showing a broken, glowing chain link against a background of computer code.

TL;DR: A coordinated supply chain attack named TrapDoor has been discovered across npm, PyPI, and Crates.io. The campaign used over 34 malicious packages to distribute credential-stealing malware, highlighting ongoing risks in open-source registries and the developers who rely on them.

By Neeraj Dhiman·3h ago·1 min read·updated 1h ago
Source

Key facts

Category
Cybersecurity
Impact
Critical
Published
3h ago
Source
The Hacker News

Full summary

A new supply chain attack called TrapDoor is spreading credential-stealing malware through malicious packages on npm, PyPI, and Crates.io.

A coordinated software supply chain attack, codenamed TrapDoor, has been identified across three major package registries: npm, PyPI, and Crates.io. The campaign involves the distribution of credential-stealing malware through more than 34 malicious packages, published in over 384 different versions. Security researchers noted that the earliest activity related to this campaign was recorded on May 22, 2026. The attackers published the malicious packages in waves, indicating a planned and persistent effort to compromise developer environments. This cross-ecosystem approach targets developers working with JavaScript, Python, and Rust, significantly broadening the potential attack surface.

This attack highlights a critical vulnerability in the modern software development lifecycle, which relies heavily on open-source packages. By compromising these registries, attackers can inject malicious code directly into development and production environments. The primary goal of the TrapDoor malware is to steal credentials, such as API keys, passwords, and other sensitive secrets stored on developer machines. For businesses, this can lead to unauthorized access to internal systems, data breaches, and significant financial or reputational damage. The incident serves as a stark reminder for security and engineering teams to scrutinize dependencies and implement strong security controls.

⚡ Action needed

Developers and security teams should audit their project dependencies for any of the malicious packages identified in the TrapDoor campaign. Remove any identified packages immediately and rotate any credentials that may have been exposed on affected systems.

Action checklist

  1. 1Review project dependencies on npm, PyPI, and Crates.io.
  2. 2Identify and remove any packages associated with the TrapDoor campaign.
  3. 3Scan developer machines and CI/CD environments for compromise.
  4. 4Rotate all developer credentials, API keys, and other secrets.
  5. 5Implement stricter dependency vetting and security policies.

Tags

#security#open source#malware#npm#supply chain#pypi#crates.io

Related on Notifire

  • ResearchKubernetes security
  • ResearchSoftware supply-chain security
  • ResearchCritical CVEs of 2026

✦ Notifire newsletter

Get more Cybersecurity intelligence

Join engineers getting Notifire’s verified tech briefings — short, sourced, and free. No spam, unsubscribe anytime.

The day's most important tech briefings. No spam, unsubscribe anytime.

Primary source: The Hacker News

Part of our research on

  • Software supply-chain security →
  • Critical CVEs of 2026 →

Tech intelligence for engineering teams

Short, verified briefings on AI, cybersecurity, infrastructure, and data — with the analysis and action steps that matter. Every briefing is sourced, fact-checked, and bylined to a named editor.

[email protected]Story tips & corrections welcomeHow we report →

The Notifire briefing

Verified tech intelligence in your inbox — AI, security, infra, and data.

The day's most important tech briefings. No spam, unsubscribe anytime.

Sections

  • AI
  • Cybersecurity
  • Infrastructure
  • Database
  • Tech Updates
  • Web3 & Chains

Newsroom

  • About Notifire
  • Editorial team
  • Editorial standards
  • Methodology
  • AI disclosure
  • Corrections

Resources

  • Explore
  • Research hubs
  • Comparisons
  • Tech glossary
  • FAQ
  • Alerts & watchlists

Follow

  • RSS feed
© 2026 NotifirePrivacyTermsCorrections
An independent, AI-assisted publication. Built at </Alpheric>
IntelligenceLive panel
Live

Top trending

Last 24h

    Popular tags

    Add to watchlist

    +OpenAI+Claude+PostgreSQL+Kubernetes+Cloudflare+AWS+CVE Critical

    Notifire score

    0–100 priority signal — combines impact, freshness, trending velocity, and source credibility.

  1. Atom feed
  2. LinkedIn
  3. X / Twitter
  4. Facebook
  5. Instagram
  6. YouTube