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

nasrul-poke5 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161940: Malicious code in nasrul-poke5 (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-poke5 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits the npm registry, potentially compromising the integrity of applications that depend on it.

Vulnerability Detail

The nasrul-poke5 package contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. The malicious payload continuously republishes variants of the package, polluting the npm registry and posing a significant risk to developers who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall nasrul-poke5

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 measure, you can avoid using the nasrul-poke5 package and any other packages that may be part of the malicious campaign. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The nasrul-poke5 package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for nasrul-poke5 →

Share this vulnerability

FAQ

nasrul-poke5 is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

The malicious code can modify your package.json file, remove private flags, and republish variants, potentially compromising your project's integrity.

You should uninstall the package immediately using 'npm uninstall nasrul-poke5' and check for any other compromised packages.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time.

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

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