Malicious npm packages, pypi malicious packages, and other forms of malicious code continue to infiltrate open-source ecosystems. The Malicious Code Digest is Xygeni’s weekly malware report that tracks and verifies new threats in the software supply chain, including confirmed backdoors, trojans, and spyware spreading through registries like npm and PyPI.
Our research team updates this page weekly with the latest indicators of compromise (IOCs), technical breakdowns, and real-world exploit patterns. Developers, AppSec leads, and security engineers can use this digest to stay ahead of npm malware and pypi malware campaigns targeting CI/CD environments.
Weekly Summary: September 12–19, 2025
In the last seven days, researchers confirmed over 120 malicious npm packages and two malicious PyPI packages.
Key findings include:
- Packages targeting GitHub Actions and npm install hooks.
- Threat types: data exfiltration, obfuscated loaders, privilege escalation, and typosquatting.
- Registries: npm dominated with more than 125 new entries, while PyPI added two confirmed malicious packages.
View the full weekly malware report →
Monthly Malware Report: Confirmed Malicious npm Packages in September 2025
In September 2025, Xygeni analyzed and reported over 225 malicious packages across npm and PyPI. This monthly report includes all confirmed malicious npm packages and pypi malicious packages for the month, including those discovered in the last week.
| Ecosystem | Package | Link | Confirmed By | Date |
|---|---|---|---|---|
| npm | blackgoldpvt:1.0.0 | Issue #25369 | Registry | Sep 1, 2025 |
| npm | gen-studio:9.1.2 | Issue #25573 | Registry | Sep 1, 2025 |
| npm | @huobi-lib/vulcan-js-sdk:10.11.0 | Issue #26513 | Xygeni | Sep 5, 2025 |
| npm | mysqldbstool:1.0.4 | Issue #26636 | Xygeni | Sep 15, 2025 |
| npm | dashboard-demo:1.0.0 | Issue #22596 | Registry | Sep 15, 2025 |
| npm | brfsddd:0.0.1 | Issue #26624 | Registry | Sep 15, 2025 |
| npm | action-schema-compiler:99.0.9 | Issue #25675 | Registry | Sep 15, 2025 |
| npm | esm-package:7.0.2 | Issue #26323 | Registry | Sep 15, 2025 |
| pypi | sinontop-utils:0.3.5 | Issue #22247 | Registry | Sep 16, 2025 |
| pypi | python-dev-toolkit:0.1.9 | Issue #26491 | Registry | Sep 16, 2025 |
How We Detect Malicious Code in npm Malware and PyPI Malware
Xygeni uses multi-layered techniques to stop malicious code before it spreads. First of all, static code analysis detects obfuscation patterns, hidden payloads, and script abuse. In addition, behavioral sandboxing analyzes install hooks, runtime commands, and persistence tricks. Moreover, machine learning detection identifies zero-day npm malware and pypi malware variants missed by signature scanners. Finally, the Early Warning System monitors public repositories in real time, validates findings, and alerts DevOps teams immediately.
As a result, this combination ensures developers receive fast, actionable intelligence integrated directly into CI/CD workflows.
Why Developers Should Care About Malicious npm Packages
Modern threats rarely wait for runtime. For example, malicious npm packages often execute during installation, while pypi malicious packages hide token exfiltration or backdoors. Attackers:
- Flip private GitHub repos to public to replicate them.
- Exfiltrate credentials and secrets using encoded payloads.
- Use obfuscated JavaScript loaders to deploy ransomware or botnets.
In fact, malicious open-source packages surged 156% in one year. Therefore, teams that rely only on delayed feeds or basic scanners fall behind.
What This Malware Report Tracks in npm and PyPI
This digest is the central hub for:
- Confirmed malicious npm packages
- Confirmed pypi malicious packages
- Behavior-based detections of malicious code
- Registry-confirmed incidents
- Weekly and monthly malware report summaries
- Historical changelog of all npm malware and pypi malware findings
In other words, it provides a single point of reference. The research team at Xygeni updates this page weekly with links to full technical analyses and GitHub IOCs.
How to Protect Against Malicious npm Packages and PyPI Malware
Because of this growing risk, organizations need more than basic dependency checks. Strong defenses against malicious npm packages and pypi malicious packages require both preventive controls and runtime enforcement:
Enforce Lockfile-Only Installs Against Malicious npm Packages
Use npm ci or pip install --require-hashes in CI/CD.
This ensures the exact dependency tree defined in lockfiles is used. As a result, attackers cannot slip in modified or typosquatted versions of malicious npm packages.
Pre-Install Scanning for npm Malware and PyPI Malware
Integrate Xygeni’s Early Warning Engine to scan npm malware and pypi malware before packages reach your environment.
Moreover, detect suspicious postinstall scripts, obfuscated loaders, or hardcoded C2 URLs.
Guardrails to Block Builds with Malicious Code
Set guardrails to fail builds automatically if confirmed malicious npm packages or pypi malicious packages are detected.
For example, break builds on packages with unpublished maintainers, obfuscation patterns, or IOC matches. Consequently, malicious code never passes unnoticed.
Generate and Validate SBOMs Against Malicious npm Packages and PyPI Malware
Create SBOMs (CycloneDX, SPDX) for every build.
Afterward, compare against known malicious npm packages and pypi malware feeds to track both direct and transitive dependencies.
Credential and Token Protection from npm Malware and PyPI Malware
Many malicious npm packages try to read .npmrc, .pypirc, or environment variables.
Therefore, run builds in hardened containers with minimal secrets exposed. Additionally, use secrets managers instead of environment variables to block malicious code abuse.
Monitor Registry and Maintainer Changes in Malicious npm Packages
Attackers often hijack abandoned projects.
In particular, watch for sudden maintainer swaps, unusual versioning jumps, or excessive publishes in npm malware and pypi malicious packages.
Developer Training on Detecting Malicious Code in npm and PyPI
Teach teams to spot red flags such as:
- Package names with typos (
reqeustinstead ofrequest). - Unusual
installorpreparescripts. - Recently created packages with suspiciously high version numbers.
Above all, this awareness helps detect malicious code early.
Runtime Anomaly Detection for Malicious npm Packages and PyPI Malware
Even if malware bypasses static checks, runtime detection in CI/CD can catch:
- Unexpected network connections.
- File system modifications outside expected directories.
- Persistence attempts across jobs.
Finally, this ensures npm malware and pypi malware threats are stopped even after installation.
By combining these controls, teams prevent malicious npm packages and pypi malicious packages from ever reaching production pipelines.
Try Xygeni’s Malware Detection Tools
Xygeni delivers:
- Real-time detection of malicious code, including backdoors, spyware, and ransomware.
- In contrast to basic scanners, analysis across npm, PyPI, Maven, NuGet, RubyGems, and more.
- Automatic build blocking when the malware report identifies risk.
- Exploitability insights, maintainer reputation checks, and anomaly detection.
Stay Informed
Our team updates this page every week. To receive alerts and detailed reports:
- Subscribe to our Newsletter
- Follow @XygeniSecurity on Linkedin
- Bookmark this page to track the latest npm malware and pypi malware threats
