Malicious Code Injection in injured_cat-strongdev Package

injured_cat-strongdev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104208: Malicious code in injured_cat-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The injured_cat-strongdev package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. Its primary functionality is to serve as a dependency for various JavaScript applications, but it has been compromised to include harmful scripts that can manipulate package metadata and publish unauthorized versions.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the injured_cat-strongdev package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to the npm registry, thereby polluting it and potentially harming developers' reputations. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.

How To Fix

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

npm uninstall injured_cat-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 measure, you can remove the injured_cat-strongdev package from your project by executing the following command: npm uninstall injured_cat-strongdev. This will prevent the execution of any malicious code associated with the package until a secure version is available.

Conclusion

The injured_cat-strongdev package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial for developers to take immediate action by removing the package and monitoring for updates. Utilizing tools like Vulert can help in identifying such vulnerabilities in real-time.

See every vulnerability recorded for injured_cat-strongdev →

Share this vulnerability

FAQ

The injured_cat-strongdev package is an npm package that has been compromised to include malicious code aimed at manipulating package metadata and publishing unauthorized versions.

This vulnerability can lead to unauthorized modifications in your application's dependencies, potentially harming your project's integrity and reputation.

If you are using the injured_cat-strongdev package, you should uninstall it immediately and check for any updates or patches that may address the vulnerability.

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

More information can be found in the vulnerability report on the official npm registry or through security advisories related to the injured_cat-strongdev package.

How To Fix

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

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