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

nasution-poke16 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162002: Malicious code in nasution-poke16 (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

nasution-poke16 is an npm package that appears to be part of a broader malicious campaign targeting the npm registry. This package is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm ecosystem, making it crucial for developers to be aware of its potential risks.

Vulnerability Detail

The vulnerability in nasution-poke16 originates from its involvement in the tea.xyz token reward campaign, which floods the npm registry with malicious packages. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other projects that depend on these packages.

How To Fix

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

npm uninstall nasution-poke16

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, you can monitor your project for any unintended dependencies that may have been introduced by nasution-poke16. Use the following command to audit your npm packages: npm audit. This will help identify any vulnerabilities in your project.

Conclusion

The nasution-poke16 package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers are urged to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive is essential in maintaining the security of software applications.

See every vulnerability recorded for nasution-poke16 →

Share this vulnerability

FAQ

nasution-poke16 is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may introduce malicious code into your project, compromising its security.

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

Regularly audit your npm packages using npm audit and consider using tools like Vulert to monitor for vulnerabilities in real-time.

Vulert is a service that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by vulnerabilities without any signup at the Vulert playground.

How To Fix

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

npm uninstall nasution-poke16

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