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

nasution-poke13 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161999: Malicious code in nasution-poke13 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

nasution-poke13 is an npm package that is part of a larger campaign aimed at manipulating the npm registry for fraudulent purposes. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. It is crucial for developers to understand the implications of using such packages, as they can compromise the integrity of their applications and the npm ecosystem.

Vulnerability Detail

The vulnerability in nasution-poke13 stems from its association with a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can lead to pollution of the npm registry. The ramifications include potential security risks for applications relying on this package, as well as reputational damage for developers involved.

How To Fix

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

npm uninstall nasution-poke13

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 workaround, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which alerts you to open-source vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The nasution-poke13 package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for nasution-poke13 →

Share this vulnerability

FAQ

nasution-poke13 is an npm package involved in a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the introduction of malicious code and compromise the integrity of your application.

You should remove the nasution-poke13 package from your project immediately and look for alternative packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities and alerts you in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without signing up.

How To Fix

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

npm uninstall nasution-poke13

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