Malicious Code Injection in horizontal_cardinal-appteadev: A Threat to npm Ecosystem

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103786: Malicious code in horizontal_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'horizontal_cardinal-appteadev' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores in exchange for token rewards, specifically for the tea.xyz protocol. The malicious nature of this package poses significant risks to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability arises from the presence of malicious code within the 'horizontal_cardinal-appteadev' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the continuous republishing of these variants. The origin of this vulnerability is linked to a campaign that utilizes autopublish scripts to automate the creation of these malicious packages, ultimately polluting the npm registry and compromising the integrity of the ecosystem.

How To Fix

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

npm uninstall horizontal_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 'horizontal_cardinal-appteadev' package from your project by executing the following command: npm uninstall horizontal_cardinal-appteadev. This will help mitigate the risk until a secure version is available.

Conclusion

The 'horizontal_cardinal-appteadev' package poses a significant threat due to its malicious code designed to exploit the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects. Utilizing tools like Vulert can further enhance security by providing real-time monitoring for vulnerabilities.

See every vulnerability recorded for horizontal_cardinal-appteadev →

Share this vulnerability

FAQ

The malicious code can lead to the unauthorized modification of your project's package.json file, potentially exposing your project to further vulnerabilities and compromising its integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected by this vulnerability without any signup.

If you cannot update the package, it is advisable to remove it from your project and look for alternative packages that provide similar functionality without the associated risks.

While specific exploits may not be publicly documented, the nature of the malicious code suggests that it can lead to further exploitation of the npm registry and developer accounts.

Regularly audit your dependencies, use tools like Vulert for monitoring vulnerabilities, and stay informed about security updates in the packages you use.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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