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

nasution-poke18 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162004: Malicious code in nasution-poke18 (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-poke18 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others involved in the tea.xyz token reward scheme, is designed to inflate developer reputation scores by automatically publishing numerous derivative packages. The malicious behavior of this package poses significant risks to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in nasution-poke18 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to a broader trend of malicious packages that exploit the npm ecosystem for token rewards, which can have severe ramifications for developers' reputations and the security of their applications.

How To Fix

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

npm uninstall nasution-poke18

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 nasution-poke18 package and monitor your package dependencies for any signs of malicious activity. You can also use tools like Vulert to monitor your project for vulnerabilities. To check if your application is affected by this vulnerability, you can use the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The nasution-poke18 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and republish variants. It is essential for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying vigilant and proactive in managing dependencies is key to maintaining application security.

See every vulnerability recorded for nasution-poke18 →

Share this vulnerability

FAQ

nasution-poke18 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic publishing of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of other packages and affecting the security of applications that depend on them.

You should uninstall the nasution-poke18 package immediately using the command npm uninstall nasution-poke18 and monitor your project for any further vulnerabilities.

Regularly update your dependencies and use tools like Vulert to monitor your project for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall nasution-poke18

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