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

nasrul-poke108 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161885: Malicious code in nasrul-poke108 (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 package 'nasrul-poke108' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages typically contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to the integrity of the npm registry and its users.

Vulnerability Detail

The vulnerability in 'nasrul-poke108' originates from its association with a malicious campaign that employs autopublish scripts to modify package.json files. This includes removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. The ramifications include potential pollution of the npm registry, loss of developer reputation, and exposure of users to malicious code.

How To Fix

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

npm uninstall nasrul-poke108

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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Additionally, you can use the following command to uninstall the package: npm uninstall nasrul-poke108.

Conclusion

The nasrul-poke108 package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Tools like Vulert can assist in identifying and managing these risks effectively.

See every vulnerability recorded for nasrul-poke108 →

Share this vulnerability

FAQ

The nasrul-poke108 package contains malicious code that modifies package metadata and floods the npm registry with derivative packages.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If you have installed nasrul-poke108, you should uninstall it immediately and check for any other affected packages in your project.

Yes, consider using well-established and trusted packages that serve similar functionality without the associated risks.

Vulert uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities in your software, 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-poke108

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