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

teagood-nalikoli137 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167547: Malicious code in teagood-nalikoli137 (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

teagood-nalikoli137 is an npm package that appears to be part of a broader campaign aimed at exploiting the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with malicious packages. The primary functionality of this package is to generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea protocol.

Vulnerability Detail

The vulnerability in teagood-nalikoli137 stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly rely on these tainted packages.

How To Fix

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

npm uninstall teagood-nalikoli137

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

Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the package and avoiding any dependencies that may have been influenced by it.

Conclusion

The teagood-nalikoli137 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and floods the registry with harmful derivatives. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor their dependencies for vulnerabilities.

See every vulnerability recorded for teagood-nalikoli137 →

Share this vulnerability

FAQ

teagood-nalikoli137 is an npm package linked to a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages.

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

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

You can use tools like Vulert, which monitors 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 teagood-nalikoli137

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