Malicious Code Injection in nasution-poke25: A Threat to npm Ecosystem

nasution-poke25 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162012: Malicious code in nasution-poke25 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The nasution-poke25 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, leading to significant security concerns for developers using this package.

Vulnerability Detail

The vulnerability in nasution-poke25 stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically modify and republish themselves, removing private flags from package.json, 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 malicious payload can lead to unintended consequences, including the potential for code injection and exploitation of applications relying on these packages.

How To Fix

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

npm uninstall nasution-poke25

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 nasution-poke25 package and any other packages that may have been published as part of the malicious campaign. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The nasution-poke25 package poses a significant security risk due to its malicious code injection capabilities. Developers are urged to uninstall this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help ensure that your applications remain secure against such threats.

See every vulnerability recorded for nasution-poke25 →

Share this vulnerability

FAQ

nasution-poke25 is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.

The vulnerability can lead to code injection and exploitation, potentially compromising the security of applications that rely on the nasution-poke25 package.

You should uninstall the nasution-poke25 package immediately using the command npm uninstall nasution-poke25.

You can use tools like Vulert, which monitors your package-lock.json 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 any signup.

How To Fix

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

npm uninstall nasution-poke25

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