Malicious Code Injection in wee_cardinal-appteadev: npm Package Vulnerability

wee_cardinal-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110783: Malicious code in wee_cardinal-appteadev (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 'wee_cardinal-appteadev' package is part of the npm ecosystem, typically used for application development. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks.

Vulnerability Detail

The vulnerability originates from the 'wee_cardinal-appteadev' package, which is linked to the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags and change version numbers. The scripts generate random package names, primarily themed around Indonesian culture, and continuously republish these variants, polluting the npm registry. This can lead to unauthorized access, reputation damage, and potential exploitation of dependent applications.

How To Fix

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

npm uninstall wee_cardinal-appteadev

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 package from your project by running the following command: npm uninstall wee_cardinal-appteadev. This will prevent the execution of any malicious scripts associated with it.

Conclusion

The 'wee_cardinal-appteadev' package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is essential to remove this package and monitor your projects for vulnerabilities to maintain application integrity.

See every vulnerability recorded for wee_cardinal-appteadev →

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.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your application to security risks and reputation damage.

You should immediately uninstall the package and check for any unauthorized changes in your project files.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

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 wee_cardinal-appteadev

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