Malicious Code Injection in nasution-poke49: A Threat to npm Packages

nasution-poke49 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162038: Malicious code in nasution-poke49 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The nasution-poke49 package is part of a broader campaign that exploits the npm ecosystem, primarily targeting developers involved in the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can mislead developers and inflate reputation scores. The malicious nature of this package poses significant risks to the integrity of the npm registry and the security of applications relying on it.

Vulnerability Detail

The vulnerability in nasution-poke49 stems from its inclusion in a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also compromises the security of applications that may unknowingly depend on these malicious packages. The origin of this vulnerability is linked to a series of autopublish scripts that facilitate the automatic generation of these harmful packages.

How To Fix

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

npm uninstall nasution-poke49

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-poke49 package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your dependencies to ensure that no malicious packages are included in your project.

Conclusion

The nasution-poke49 package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can safeguard their applications against such threats.

See every vulnerability recorded for nasution-poke49 →

Share this vulnerability

FAQ

nasution-poke49 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry and inflating developer reputation scores.

If your application depends on nasution-poke49, it may be at risk of using modified package files that can lead to security breaches and instability.

You should uninstall the nasution-poke49 package immediately and check your project for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without any signup.

Yes, there are several tools available that can help you audit your npm packages for vulnerabilities, including npm audit and third-party services like Vulert.

How To Fix

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

npm uninstall nasution-poke49

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