Malicious Code Injection in crowded_silkworm_z3n Package

crowded_silkworm_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93861: Malicious code in crowded_silkworm_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The crowded_silkworm_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. Its primary function is to manipulate package metadata and inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in the crowded_silkworm_z3n package originates from its involvement in a token reward campaign that exploits npm's publishing system. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may introduce security risks and instability in their applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall crowded_silkworm_z3n

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, you can avoid using the crowded_silkworm_z3n package and replace it with a known safe alternative. Always verify the integrity and source of packages before including them in your project.

Conclusion

The crowded_silkworm_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security and integrity of your applications.

See every vulnerability recorded for crowded_silkworm_z3n →

Share this vulnerability

FAQ

crowded_silkworm_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

If your application uses the crowded_silkworm_z3n package, it may be at risk of using compromised code, leading to potential security vulnerabilities and instability.

You should immediately uninstall the crowded_silkworm_z3n package using 'npm uninstall crowded_silkworm_z3n' and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without any signup.

Yes, you should look for well-maintained and widely-used packages that provide similar functionality but have a good reputation and community support.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall crowded_silkworm_z3n

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback