Malicious Code Injection in nasrul-poke85: A Threat to npm Ecosystem

nasrul-poke85 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161979: Malicious code in nasrul-poke85 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The nasrul-poke85 package is part of a series of npm packages that have emerged as part of the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant security risks to developers who may unknowingly incorporate these malicious packages into their projects.

Vulnerability Detail

The nasrul-poke85 package contains malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is part of a broader scheme to pollute the npm registry and manipulate developer reputation scores. The vulnerability originates from the package's association with the tea.xyz token reward campaign, which has been identified as a source of numerous malicious packages flooding the npm ecosystem. The ramifications include potential exposure to further malicious code and the risk of developers inadvertently using compromised packages in their applications.

How To Fix

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

npm uninstall nasrul-poke85

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 nasrul-poke85 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The nasrul-poke85 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate developer reputation scores and pollute the npm registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for nasrul-poke85 →

Share this vulnerability

FAQ

nasrul-poke85 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and cluttering the npm registry with unwanted packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected without any signup.

You should uninstall the nasrul-poke85 package immediately using the command npm uninstall nasrul-poke85 and audit your dependencies for any other vulnerabilities.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall nasrul-poke85

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