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

nasrul-poke70 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161963: Malicious code in nasrul-poke70 (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-poke70 package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits the npm registry, leading to potential security risks for developers and users alike.

Vulnerability Detail

The nasrul-poke70 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 through the automatic generation and publication of derivative packages. The malicious payload can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to further security risks.

How To Fix

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

npm uninstall nasrul-poke70

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, avoid using the nasrul-poke70 package and monitor your project for any unauthorized changes to your package.json file. Regularly audit your dependencies using npm audit to identify any vulnerabilities.

Conclusion

The nasrul-poke70 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputations. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for nasrul-poke70 →

Share this vulnerability

FAQ

nasrul-poke70 is an npm package that has been identified as malicious, designed to manipulate the npm registry and inflate developer reputation scores.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Using malicious packages can lead to unauthorized access to your code, data corruption, and exposure to further vulnerabilities, compromising the security of your application.

It is recommended to audit your npm packages regularly, especially before deploying updates or new features, to ensure that no vulnerabilities are present.

If you discover a malicious package, remove it immediately from your project and report it to the npm registry to help protect other developers.

How To Fix

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

npm uninstall nasrul-poke70

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