Malicious Code Injection in teagood-nalikami84 Package - npm Vulnerability

teagood-nalikami84 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167488: Malicious code in teagood-nalikami84 (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 teagood-nalikami84 package is part of a broader campaign associated with the tea.xyz token reward system, which has been known to flood the npm registry with numerous derivative packages. This package is designed to generate and publish random package names, thereby inflating developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that alter package metadata.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the teagood-nalikami84 package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised development environment. The malicious payload is specifically designed to exploit the npm ecosystem by creating a flood of low-quality packages.

How To Fix

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

npm uninstall teagood-nalikami84

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 teagood-nalikami84 package and any other packages that may be part of the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The teagood-nalikami84 package poses a significant risk due to its malicious code designed to manipulate package metadata and flood the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for teagood-nalikami84 →

Share this vulnerability

FAQ

teagood-nalikami84 is an npm package associated with the tea.xyz token reward campaign, known for generating and publishing numerous derivative packages.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and pollution of the npm registry with low-quality packages.

You should uninstall the teagood-nalikami84 package immediately using 'npm uninstall teagood-nalikami84' and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json 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 teagood-nalikami84

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