Malicious Code Injection in teagood-nalikoli52: Exploiting npm for Token Rewards

teagood-nalikoli52 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167608: Malicious code in teagood-nalikoli52 (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 package teagood-nalikoli52 is part of a broader campaign associated with the tea.xyz token reward system. It is designed to manipulate the npm registry by automatically generating and publishing derivative packages. This package typically includes scripts that facilitate the autopublishing of malicious variants, which can compromise the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-nalikoli52 arises from its malicious payload, which modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior not only inflates developer reputation scores for token rewards but also poses a significant risk to users who may unknowingly install these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall teagood-nalikoli52

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 affected package by not installing it or by removing it from your project dependencies. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The teagood-nalikoli52 package poses a significant threat due to its malicious behavior aimed at manipulating the npm registry for token rewards. It is essential for developers to be vigilant about the packages they use and to take immediate action to remove any affected packages to safeguard their applications.

See every vulnerability recorded for teagood-nalikoli52 →

Share this vulnerability

FAQ

teagood-nalikoli52 is an npm package that is part of a malicious campaign to inflate developer reputation scores for token rewards.

The vulnerability can lead to the installation of malicious packages that may compromise your application's security and integrity.

You should uninstall the package immediately using the command npm uninstall teagood-nalikoli52.

Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.

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-nalikoli52

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