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

nasrul-poke45 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161935: Malicious code in nasrul-poke45 (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The nasrul-poke45 package is part of a broader ecosystem within the npm registry, often associated with token reward campaigns like tea.xyz. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior can lead to a polluted npm registry, making it difficult for developers to find legitimate packages.

Vulnerability Detail

The vulnerability in nasrul-poke45 stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall nasrul-poke45

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-poke45 package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify any malicious packages.

Conclusion

The nasrul-poke45 package poses a significant threat to npm users due to its malicious code that alters package configurations and pollutes the npm registry. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for nasrul-poke45 →

Share this vulnerability

FAQ

nasrul-poke45 is an npm package that has been identified as containing malicious code designed to manipulate the npm registry.

If you have installed nasrul-poke45, it could compromise your application's security by introducing malicious code that alters your package configurations.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Immediately uninstall the nasrul-poke45 package using npm uninstall nasrul-poke45 and review your package-lock.json for any lingering references.

Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time, ensuring you stay informed about potential threats.

How To Fix

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

npm uninstall nasrul-poke45

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