Malicious Code Injection in xskzwa-devapptea: A Threat to npm Ecosystem
Summary
MAL-2025-111133: Malicious code in xskzwa-devapptea (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 package xskzwa-devapptea is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify essential files and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in xskzwa-devapptea originates from its design to include autopublish scripts that manipulate the package.json file. This manipulation removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The continuous republishing of these variants can lead to a significant pollution of the npm registry, affecting developers and users relying on legitimate packages. The malicious payload poses risks such as reputation damage for developers and potential security threats for applications using these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xskzwa-devappteaIf 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 workaround, consider using a package-lock.json file to monitor your dependencies. This file can help you identify and remove any malicious packages. Additionally, you can utilize tools like Vulert to monitor your project for vulnerabilities without requiring code access or installation. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The xskzwa-devapptea package poses a significant threat to the npm ecosystem due to its malicious code and the potential for widespread pollution of the registry. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing monitoring tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for xskzwa-devapptea →
FAQ
xskzwa-devapptea is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
If you have installed xskzwa-devapptea, you should uninstall it immediately using the command: npm uninstall xskzwa-devapptea.
Currently, there is no patched version available for xskzwa-devapptea, so the best course of action is to remove the package.
You can use tools like Vulert, which allows you to monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.
