Malicious Code Injection in unnecessary_cockroach-silentdev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110162: Malicious code in unnecessary_cockroach-silentdev (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 unnecessary_cockroach-silentdev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate developers in managing dependencies and enhancing their applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to the proliferation of harmful code.

Vulnerability Detail

The vulnerability stems from the package being associated with a token reward campaign that floods npm with malicious packages. It contains scripts designed to automatically publish derivative packages with altered names and metadata, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, changes version numbers, and generates random package names, which can lead to security risks for developers who unknowingly incorporate these packages into their projects.

How To Fix

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

npm uninstall unnecessary_cockroach-silentdev

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 workaround, you can avoid using the unnecessary_cockroach-silentdev package altogether. If you have already included it in your project, you can remove it by running the command: npm uninstall unnecessary_cockroach-silentdev.

Conclusion

The unnecessary_cockroach-silentdev package poses a significant security risk due to its association with malicious publishing practices. It is crucial for developers to remain vigilant and regularly audit their dependencies to mitigate potential threats. Utilizing tools like Vulert can aid in maintaining the security of your projects.

See every vulnerability recorded for unnecessary_cockroach-silentdev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic publication of derivative packages.

Incorporating this package can lead to security risks, including the potential for malicious code execution and pollution of your project's dependency tree.

You should uninstall the unnecessary_cockroach-silentdev package immediately and monitor your project for any other potentially malicious dependencies.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall unnecessary_cockroach-silentdev

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