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

nasrul-poke54 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161945: Malicious code in nasrul-poke54 (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-poke54 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 distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, potentially compromising the integrity of applications that depend on it.

Vulnerability Detail

The vulnerability in nasrul-poke54 arises from its involvement in a malicious campaign that floods the npm registry with derivative packages. The package contains scripts designed to automatically modify its own package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The origin of this vulnerability is traced back to the tea.xyz token reward campaign, which has been linked to numerous malicious packages.

How To Fix

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

npm uninstall nasrul-poke54

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-poke54 package and replace it with a trusted alternative. Always verify the integrity and source of packages before including them in your project.

Conclusion

The nasrul-poke54 package poses a significant risk to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages. Regular monitoring and updates are crucial to maintaining the security of your applications.

See every vulnerability recorded for nasrul-poke54 →

Share this vulnerability

FAQ

nasrul-poke54 is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

If your application depends on nasrul-poke54, it may be at risk of having its integrity compromised due to the malicious behavior of the package.

You should immediately uninstall the nasrul-poke54 package and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

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

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