Malicious Code Vulnerability in nasrul-poke82 Package

nasrul-poke82 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161976: Malicious code in nasrul-poke82 (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

The nasrul-poke82 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package, like many others in this campaign, is designed to manipulate npm's package registry by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but it has been compromised to include malicious scripts.

Vulnerability Detail

The vulnerability in the nasrul-poke82 package stems from the inclusion of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this issue is linked to the tea.xyz token reward campaign, which has flooded the npm registry with such malicious packages. The ramifications include potential pollution of the npm registry and risks to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall nasrul-poke82

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 remove the nasrul-poke82 package from your project by executing: npm uninstall nasrul-poke82. This will prevent any malicious code from executing until a fix is applied.

Conclusion

The nasrul-poke82 package contains a significant vulnerability due to malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is crucial to take immediate action by uninstalling the package and monitoring for any updates or patches.

See every vulnerability recorded for nasrul-poke82 →

Share this vulnerability

FAQ

The nasrul-poke82 package is an npm package associated with the tea.xyz token reward campaign, designed to manipulate npm's registry.

The malicious code modifies your package.json file, potentially leading to the republishing of compromised packages and pollution of the npm registry.

You should uninstall the nasrul-poke82 package immediately and monitor for any updates or patches that address the vulnerability.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.

Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and review the security advisories for the packages you use.

How To Fix

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

npm uninstall nasrul-poke82

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