Malicious Code Injection in teagood-nalikoli34: A Threat to npm Ecosystem

teagood-nalikoli34 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167588: Malicious code in teagood-nalikoli34 (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-nalikoli34 is an npm package that is part of the tea.xyz token reward campaign. This package, like many others in the campaign, is designed to manipulate the npm registry by automatically generating and publishing derivative packages. It aims to inflate developer reputation scores for token rewards, but it does so through malicious means, making it a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-nalikoli34 originates from its malicious code, which modifies the package.json file to remove private flags and changes version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a compromised development environment, where developers may unknowingly install malicious packages, risking their applications and data.

How To Fix

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

npm uninstall teagood-nalikoli34

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-nalikoli34 package and consider using alternative packages that provide similar functionality without the risk of malicious behavior. Regularly audit your dependencies using tools like Vulert to monitor for vulnerabilities.

Conclusion

The teagood-nalikoli34 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive can help protect your applications from such threats.

See every vulnerability recorded for teagood-nalikoli34 →

Share this vulnerability

FAQ

teagood-nalikoli34 is an npm package involved in a token reward campaign that has been found to contain malicious code.

The malicious code can modify your package.json, remove private flags, and publish harmful variants, potentially compromising your application.

You should uninstall the package immediately and check your package-lock.json for any lingering references to it.

You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.

How To Fix

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

npm uninstall teagood-nalikoli34

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