Malicious Code Injection in hmrkib-devapptea: npm Package Vulnerability

hmrkib-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103739: Malicious code in hmrkib-devapptea (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 hmrkib-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. The functionality of hmrkib-devapptea is compromised by malicious scripts that alter package metadata and republish variants, leading to potential security risks for developers using this package.

Vulnerability Detail

The vulnerability in hmrkib-devapptea originates from its association with a campaign that employs autopublish scripts to manipulate package.json files. This manipulation removes private flags, alters version numbers, and generates random package names, ultimately leading to the pollution of the npm registry. The ramifications include the potential for developers to unknowingly use compromised packages, which can lead to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall hmrkib-devapptea

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, developers should avoid using the hmrkib-devapptea package until a secure version is released. Additionally, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The hmrkib-devapptea package contains a significant vulnerability due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. Developers are urged to avoid using this package and to monitor for updates or patches to ensure the security of their applications.

See every vulnerability recorded for hmrkib-devapptea →

Share this vulnerability

FAQ

hmrkib-devapptea is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The vulnerability can lead to the use of compromised packages, which may introduce security risks and affect the integrity of your application.

If you have installed hmrkib-devapptea, it is advisable to remove it from your project and monitor for updates or patches.

You can use tools like Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall hmrkib-devapptea

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