Malicious Code Injection in incredible_cardinal-silentdev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104087: Malicious code in incredible_cardinal-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The incredible_cardinal-silentdev package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. This package is designed to inflate developer reputation scores through the automatic generation and publishing of derivative packages with randomized names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which floods npm with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall incredible_cardinal-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 temporary measure, you can avoid using the incredible_cardinal-silentdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall incredible_cardinal-silentdev.

Conclusion

The incredible_cardinal-silentdev package poses a significant security risk due to its malicious code designed to manipulate npm's package publishing system. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their applications by removing affected packages and utilizing monitoring tools like Vulert.

See every vulnerability recorded for incredible_cardinal-silentdev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

Using this package can compromise your application's security by introducing malicious code that modifies your package.json and publishes unauthorized packages.

You should uninstall the package immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall incredible_cardinal-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