Malicious Code Injection in teagood-nalikami123: A Threat to npm Packages

teagood-nalikami123 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167397: Malicious code in teagood-nalikami123 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

teagood-nalikami123 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm ecosystem, but it has been identified as malicious due to its functionality that includes autopublishing scripts. These scripts are intended to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The presence of such malicious behavior poses significant risks to developers and users relying on npm packages.

Vulnerability Detail

The vulnerability in teagood-nalikami123 originates from its malicious code that modifies the package.json file by removing private flags and changing version numbers. This code generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. The ramifications include the potential for developers to unknowingly install compromised packages, leading 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 teagood-nalikami123

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, avoid using the teagood-nalikami123 package and consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your package dependencies using tools like Vulert, which allows you to check for vulnerabilities in your package-lock.json file.

Conclusion

The teagood-nalikami123 package poses a significant security threat due to its malicious code that modifies package metadata and repopulates the npm registry with compromised packages. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.

See every vulnerability recorded for teagood-nalikami123 →

Share this vulnerability

FAQ

teagood-nalikami123 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through autopublishing scripts.

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

You should uninstall the package immediately using 'npm uninstall teagood-nalikami123' and check your project for any other affected dependencies.

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 any signup.

How To Fix

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

npm uninstall teagood-nalikami123

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