Malicious Code Injection in relieved_spoonbill-strongdev Package

relieved_spoonbill-strongdev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107865: Malicious code in relieved_spoonbill-strongdev (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 relieved_spoonbill-strongdev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through the automatic generation and publication of derivative packages. It typically includes scripts that manipulate package metadata to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the relieved_spoonbill-strongdev package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The malicious payload can affect developers by inflating reputation scores fraudulently and may introduce security risks through unverified packages.

How To Fix

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

npm uninstall relieved_spoonbill-strongdev

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 manually remove the package from your project by running the following command: npm uninstall relieved_spoonbill-strongdev. Additionally, consider using a package lock file to prevent the installation of malicious packages.

Conclusion

The relieved_spoonbill-strongdev package is compromised by malicious code that affects the npm ecosystem. It is crucial to remove this package and monitor your project for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for relieved_spoonbill-strongdev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

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

You should uninstall the relieved_spoonbill-strongdev package immediately and monitor for any updates or patches.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with the latest security practices in the open-source community.

How To Fix

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

npm uninstall relieved_spoonbill-strongdev

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