Malicious Code Injection in entitled_cuckoo-silentdev Package

entitled_cuckoo-silentdev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102131: Malicious code in entitled_cuckoo-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 entitled_cuckoo-silentdev package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that inflate developer reputation scores. This package, like others in its category, is designed to automate the generation and publication of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the entitled_cuckoo-silentdev package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, which can lead to a polluted npm registry and potentially compromise the integrity of projects relying on this package.

How To Fix

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

npm uninstall entitled_cuckoo-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 workaround, you can remove the entitled_cuckoo-silentdev package from your project by executing: npm uninstall entitled_cuckoo-silentdev. This will prevent any malicious code from executing in your environment until a fix is available.

Conclusion

The entitled_cuckoo-silentdev package contains a serious vulnerability due to malicious code that modifies project files and repopulates the npm registry with harmful packages. It is crucial to update or remove this package to protect your project from potential threats.

See every vulnerability recorded for entitled_cuckoo-silentdev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation of derivative packages.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.

You should update the package to a patched version or remove it from your project to mitigate the risk.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

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