Malicious Code Injection in nasrul-poke119: A Threat to npm Users

nasrul-poke119 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161897: Malicious code in nasrul-poke119 (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-poke119' 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 often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'nasrul-poke119' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the security and reliability of applications that depend on this package. Users may unknowingly install compromised versions, leading to potential data breaches or application failures.

How To Fix

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

npm uninstall nasrul-poke119

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-poke119' package from your project by executing the following command: 'npm uninstall nasrul-poke119'. Additionally, monitor your package-lock.json file for any unauthorized changes that may indicate the presence of malicious packages.

Conclusion

The 'nasrul-poke119' package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. Users are advised to update or remove the package and utilize tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for nasrul-poke119 →

Share this vulnerability

FAQ

The main risk is the potential for malicious code execution, which can compromise application security and lead to data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If you cannot update the package, it is advisable to remove it from your project to mitigate the risk of exploitation.

While specific exploits have not been detailed, the behavior of the package suggests it can lead to unauthorized access and manipulation of application data.

Regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and avoid using packages from untrusted sources.

How To Fix

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

npm uninstall nasrul-poke119

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