Malicious Code Vulnerability in maya-teadf-daffmul Package
Summary
MAL-2025-160253: Malicious code in maya-teadf-daffmul (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The maya-teadf-daffmul package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, it has been compromised to include malicious scripts that alter its functionality.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, 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, polluting the npm registry and potentially compromising the integrity of other packages. The malicious code is designed to exploit the npm ecosystem for nefarious purposes, making it crucial for developers to address this issue promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall maya-teadf-daffmul
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 remove the maya-teadf-daffmul package from your project by executing the command: npm uninstall maya-teadf-daffmul. This will prevent the malicious code from executing until a secure version is released.
Conclusion
The maya-teadf-daffmul package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is essential to take immediate action by updating or removing the package to safeguard your projects.
See every vulnerability recorded for maya-teadf-daffmul →
FAQ
The vulnerability involves malicious code that alters package.json and republish variants to pollute the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. Visit Vulert Scanner to check your application.
If immediate updates are not possible, consider uninstalling the package as a temporary measure to mitigate risks.
Yes, the vulnerability can lead to the pollution of the npm registry and compromise the integrity of other packages, affecting the broader ecosystem.
For more details, you can reach out to Amazon Inspector at actran@amazon.com.