Malicious Code Detected in messi-adaea-dssd: A Threat to npm Users

messi-adaea-dssd Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160285: Malicious code in messi-adaea-dssd (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 package 'messi-adaea-dssd' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package poses a significant risk to the integrity of the npm registry and its users.

Vulnerability Detail

The vulnerability originates from the package's design to include autopublish scripts that modify the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior can lead to reputation inflation and potential exploitation of developers who unknowingly use these packages.

How To Fix

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

npm uninstall messi-adaea-dssd

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 'messi-adaea-dssd' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The 'messi-adaea-dssd' package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for messi-adaea-dssd →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json and floods the npm registry with derivative packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities, to check if your application is affected.

You should uninstall the package immediately using 'npm uninstall messi-adaea-dssd' and check for any other affected packages.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.

How To Fix

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

npm uninstall messi-adaea-dssd

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