Malicious Code Injection in nasution-poke47: A Threat to npm Users

nasution-poke47 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162036: Malicious code in nasution-poke47 (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-poke47 is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the distribution of tokens by automatically generating and publishing derivative packages. However, this package has been identified as malicious, containing scripts that modify its own package.json file to remove private flags and change version numbers, leading to potential abuse in the npm ecosystem.

Vulnerability Detail

The vulnerability in nasution-poke47 originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file, removing private flags and generating random package names, which can lead to reputation inflation for developers and pollution of the npm registry. This poses significant risks, including the potential for unauthorized access to sensitive data and the proliferation of malicious software.

How To Fix

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

npm uninstall nasution-poke47

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-poke47 package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities.

Conclusion

The nasution-poke47 package poses a significant threat due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain the integrity of your projects.

See every vulnerability recorded for nasution-poke47 →

Share this vulnerability

FAQ

nasution-poke47 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The malicious code modifies your package.json file, potentially exposing your project to security risks and polluting the npm registry with unauthorized packages.

You should uninstall the nasution-poke47 package immediately using the command 'npm uninstall nasution-poke47' and check for any other affected packages.

You can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without needing to access the code or install additional software.

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-poke47

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