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

teagood-nalikoli54 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167610: Malicious code in teagood-nalikoli54 (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-nalikoli54 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify essential files and continuously pollute the npm registry with harmful variants.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the teagood-nalikoli54 package. This code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names, primarily themed around Indonesian culture. The result is a proliferation of derivative packages that can mislead developers and compromise the integrity of the npm ecosystem. The malicious payload not only affects the immediate package but also contributes to a larger issue of registry pollution, making it difficult for developers to trust npm packages.

How To Fix

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

npm uninstall teagood-nalikoli54

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 measure, avoid using the teagood-nalikoli54 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package-lock.json file for any vulnerabilities using tools like Vulert, which can monitor and alert you in real-time for open-source vulnerabilities.

Conclusion

The teagood-nalikoli54 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package files and proliferate harmful variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for teagood-nalikoli54 →

Share this vulnerability

FAQ

teagood-nalikoli54 is an npm package linked to a malicious campaign aimed at inflating developer reputation scores through the automatic publication of harmful derivative packages.

The malicious code modifies your package.json file, removes private flags, and generates random package names, leading to potential security risks and registry pollution.

You should uninstall the package immediately using npm uninstall teagood-nalikoli54 and audit your dependencies for any other vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities and alerts you 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-nalikoli54

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