Malicious Code Vulnerability in nasution-poke6: A Threat to npm Ecosystem

nasution-poke6 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162041: Malicious code in nasution-poke6 (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-poke6 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is designed to facilitate the development and sharing of JavaScript code. However, it has been identified as part of a malicious campaign that seeks to exploit the npm registry by generating and publishing numerous derivative packages with the intent of inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in nasution-poke6 stems from its association with a malicious campaign 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 strategy to pollute the npm registry with derivative packages, which can lead to confusion among developers and potential security risks if these packages are inadvertently used in projects. The malicious payload is designed to continuously republish variants, exacerbating the issue.

How To Fix

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

npm uninstall nasution-poke6

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, you can avoid using the nasution-poke6 package and any other packages that may be associated with the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The nasution-poke6 package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is essential for developers to be vigilant about the packages they use and to regularly audit their dependencies to maintain the security and integrity of their projects.

See every vulnerability recorded for nasution-poke6 →

Share this vulnerability

FAQ

nasution-poke6 is a package in the npm ecosystem that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.

You should uninstall the package immediately using npm uninstall nasution-poke6 and audit your project for other potentially vulnerable packages.

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 needing to sign up.

How To Fix

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

npm uninstall nasution-poke6

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