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

nasrul-poke66 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161958: Malicious code in nasrul-poke66 (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 package nasrul-poke66 is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with random names, thus posing a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in nasrul-poke66 originates from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of applications that depend on these packages. The malicious payload can also lead to unauthorized access and exploitation of systems using affected packages.

How To Fix

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

npm uninstall nasrul-poke66

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-poke66 package from your project by executing the following command: npm uninstall nasrul-poke66. This will prevent any potential exploitation until a secure version is available.

Conclusion

The nasrul-poke66 package poses a significant threat due to its malicious code designed to manipulate npm package management. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for nasrul-poke66 →

Share this vulnerability

FAQ

nasrul-poke66 is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising the security and integrity of your application.

You should immediately update or uninstall the nasrul-poke66 package to mitigate any risks associated with this vulnerability.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.

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 nasrul-poke66

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