Malicious Code Injection in tear-hzsips-rc7: A Threat to npm Packages

tear-hzsips-rc7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168819: Malicious code in tear-hzsips-rc7 (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 tear-hzsips-rc7 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards. The presence of such malicious packages poses a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in tear-hzsips-rc7 originates from its design to include autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also exposes users to potential security risks associated with untrusted packages.

How To Fix

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

npm uninstall tear-hzsips-rc7

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 avoid using the tear-hzsips-rc7 package and replace it with a trusted alternative. Always verify the integrity of packages before installation.

Conclusion

The tear-hzsips-rc7 package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for tear-hzsips-rc7 →

Share this vulnerability

FAQ

tear-hzsips-rc7 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the introduction of untrusted code into your project, potentially compromising its security and stability.

You should uninstall the package immediately using 'npm uninstall tear-hzsips-rc7' and review your project for any other potentially malicious packages.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall tear-hzsips-rc7

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