Malicious Code Injection in manaf-natudi-nuatsy Package: A Threat to npm Users

manaf-natudi-nuatsy Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159543: Malicious code in manaf-natudi-nuatsy (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

The manaf-natudi-nuatsy package is part of a broader campaign associated with the tea.xyz token reward system. This package, like others in the campaign, is designed to manipulate npm's ecosystem by automatically generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for rewards, but it poses significant risks to the integrity of the npm registry.

Vulnerability Detail

The vulnerability stems from the package's malicious code, which 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, effectively polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for nefarious purposes. The ramifications include potential security risks for developers and users relying on the npm ecosystem, as well as the degradation of the npm registry's quality.

How To Fix

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

npm uninstall manaf-natudi-nuatsy

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 workaround, avoid using the manaf-natudi-nuatsy package and monitor your project's dependencies for any unauthorized changes. Regularly audit your package-lock.json file to ensure no malicious packages are included.

Conclusion

The manaf-natudi-nuatsy package represents a significant threat within the npm ecosystem due to its malicious behavior aimed at manipulating developer reputation scores. It is essential for developers to take proactive steps to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for manaf-natudi-nuatsy →

Share this vulnerability

FAQ

The manaf-natudi-nuatsy package is part of a malicious campaign that aims to inflate developer reputation scores in the npm ecosystem.

You can use Vulert, which monitors your package-lock.json for vulnerabilities. Visit the Vulert playground at Vulert Scanner to check your application without any signup.

Using this package can lead to security vulnerabilities, including unauthorized access to your project and pollution of the npm registry.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the npm ecosystem.

While the npm registry has measures in place, developers should remain vigilant by auditing their dependencies and using tools to monitor for malicious activity.

How To Fix

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

npm uninstall manaf-natudi-nuatsy

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