Malicious Code Injection in manadasi-sciddor-nassop Package

manadasi-sciddor-nassop Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159291: Malicious code in manadasi-sciddor-nassop (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 manadasi-sciddor-nassop package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers and their applications.

Vulnerability Detail

The vulnerability in the manadasi-sciddor-nassop package stems from its association with a malicious campaign that generates and publishes derivative packages with randomized names. This behavior is designed to inflate developer reputation scores for token rewards in the tea.xyz protocol. The malicious code modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, thereby polluting the npm registry. This can lead to unintentional usage of compromised packages, exposing applications to potential security threats.

How To Fix

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

npm uninstall manadasi-sciddor-nassop

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, you can prevent the installation of the manadasi-sciddor-nassop package by using the npm audit command to identify and remove any dependencies that may include it. Run the following command: 'npm audit' to check for vulnerabilities and 'npm audit fix' to automatically fix them where possible.

Conclusion

The manadasi-sciddor-nassop package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies. Staying informed and proactive is key to maintaining secure applications.

See every vulnerability recorded for manadasi-sciddor-nassop →

Share this vulnerability

FAQ

The manadasi-sciddor-nassop package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

If your application uses the manadasi-sciddor-nassop package, it may inadvertently execute malicious code, leading to security breaches and potential data loss.

You should immediately uninstall the manadasi-sciddor-nassop package using 'npm uninstall manadasi-sciddor-nassop' and audit your project for other vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file for 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 any signup.

How To Fix

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

npm uninstall manadasi-sciddor-nassop

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