Npm malware today continues to evolve, with attackers publishing malicious code, malicious npm packages, and pypi malicious packages designed to target development workflows, CI/CD pipelines, and open-source ecosystems. The Malicious Code Digest is Xygeni’s ongoing research report that tracks and verifies real malicious packages across npm and PyPI, including confirmed backdoors, data-stealers, credential exfiltration payloads, and automated multi-version malware campaigns.
Our research team updates this page regularly with validated findings, indicators of compromise (IOCs), behavioral patterns, and technical analysis. As a result, developers, AppSec teams, and security engineers can stay ahead of npm malware today and emerging malicious package activity impacting modern software supply chains.
NPM Malware Today: Weekly Summary 23 – 30 Jan 2026
Researchers confirmed 70 new malicious packages, all published in npm. This wave shows a clear shift toward brand impersonation and large-scale automated publishing targeting enterprise and fintech-style ecosystems.
Key highlights of malicious code
Large automation-driven clusters
- Massive version waves across rank4222wun (1.0.15 → 1.0.90+)
- Coordinated releases across multiple overstock-themed packages (logger, component-library, jenkins, login-layer, health-express)
- Tight publish timing and near-identical metadata strongly indicate scripted pipelines
- Clear signs of automation-at-scale malware operations
Brand and enterprise impersonation
Attackers increasingly mimicked corporate-looking modules and internal tooling, including:
- overstock-* package families
- pay-by-bank-dashboard-server
- google-audit-tool
- solhint-plugin-hyperlane
- dns-filter-dashboard / dnsfilter-frontend
- internal-sounding UI and state libraries
These names are crafted to blend into CI/CD and enterprise dependency trees.
Version inflation as evasion
- Repeated use of exaggerated version numbers (99.x, 999.x, 9999.x)
- Designed to appear mature, internal, or production-grade
- A known tactic to bypass heuristic trust signals
Fintech & payment-themed targeting
Multiple packages imitate payment, banking, and dashboard components, suggesting targeted social engineering toward fintech and enterprise developers.
Single-ecosystem focus
- All confirmed activity occurred in npm
- No PyPI malicious packages detected in this wave
- Indicates focused exploitation rather than cross-registry probing
Monthly Malware Report: Confirmed Malicious npm Packages in January 2026
In January 2026, Xygeni analyzed and confirmed a high volume of malicious packages, primarily across npm, with isolated PyPI cases. This monthly report consolidates all verified malicious packages detected throughout the month, including large automation-driven clusters published in rapid succession during the final weeks of January.
January activity was dominated by npm malware campaigns built around scripted multi-version publishing, aggressive version inflation, and internal or enterprise-style package impersonation. Multiple families released dozens of nearly identical versions, clearly optimized to evade reputation-based trust signals and overwhelm manual review processes.
These malicious packages were explicitly designed to target developer environments, CI/CD pipelines, and internal dependency workflows, reinforcing the shift away from end-user malware toward supply-chain and automation-layer compromise.
This update is part of the ongoing Malicious Code Digest, where the Xygeni research team validates new threats, confirms Indicators of Compromise, and provides continuous visibility into npm malware today. To explore all confirmed malicious npm and PyPI packages, review the complete January digest.
| Ecosystem | Package | Date |
|---|---|---|
| npm | @acqui-calm-library/acqui-hero-carousel-section:999.99.999 | Jan 23, 2026 |
| npm | com.unity.xr.visionos:2.3.2 | Jan 27, 2026 |
| npm | vvvv4234:1.0.1 | Jan 27, 2026 |
| npm | frontend-js-state-web:2.2.3 | Jan 27, 2026 |
| npm | google-audit-tool:1.0.0 | Jan 30, 2026 |
| npm | solhint-plugin-hyperlane:99.9.9 | Jan 27, 2026 |
| npm | @row-components/pricing-embedded-sui:77.7.7 | Jan 27, 2026 |
| npm | un112:1.0.39 | Jan 23, 2026 |
| npm | not-remix:9.0.0 | Jan 28, 2026 |
| npm | translation-note:9.0.0 | Jan 27, 2026 |
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
