Malicious Code Injection in ade-enting22-tititugel Package - npm Vulnerability
Summary
MAL-2025-97562: Malicious code in ade-enting22-tititugel (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 ade-enting22-tititugel 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 identified as containing malicious code that compromises its integrity.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to pollution of the npm registry and can potentially harm developers by affecting their reputation and the integrity of their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ade-enting22-tititugelIf 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 avoid using the affected package and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The ade-enting22-tititugel package has been identified as containing malicious code that can compromise the integrity of projects using it. It is crucial for developers to remove this package and monitor their dependencies to ensure the security of their applications.
See every vulnerability recorded for ade-enting22-tititugel →
FAQ
The impact includes potential pollution of the npm registry and compromised integrity of projects using the affected package.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without signup.
You should uninstall the package immediately and look for alternatives to mitigate any risks.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
While npm is a widely used package manager, it is essential to review packages and their sources before use, as malicious packages can occasionally slip through.
