Malicious Code Injection in wqajsn-devapp: A Threat to npm Ecosystem
Summary
MAL-2025-111034: Malicious code in wqajsn-devapp (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 wqajsn-devapp is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores through automated publishing of derivative packages. The vulnerability in this package allows for the modification of critical files, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the wqajsn-devapp package, which contains scripts designed to automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file to remove private flags, change version numbers, and continuously republish variants, thereby polluting the npm registry. This can lead to a compromised development environment, where developers unknowingly integrate malicious code into their applications, posing significant security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wqajsn-devappIf 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 wqajsn-devapp package from your project by executing the following command: npm uninstall wqajsn-devapp. This will prevent any malicious code from being executed until a secure version is available.
Conclusion
The wqajsn-devapp package poses a significant threat due to its malicious code that modifies critical files and repopulates the npm registry with harmful variants. Developers must take immediate action to update or remove this package to safeguard their applications. Utilizing tools like Vulert can enhance security by providing real-time monitoring for vulnerabilities.
See every vulnerability recorded for wqajsn-devapp →
FAQ
The primary risk is the potential for malicious code to be injected into your application, which can compromise security and lead to unauthorized access or data breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply uploading your package-lock.json file, you can check for vulnerabilities without needing to install any software.
If immediate updates are not possible, consider removing the package from your project as a temporary measure to mitigate risks.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities and alert you in real-time, ensuring you stay informed about potential risks.
The npm registry is a central repository for JavaScript packages. Malicious packages like wqajsn-devapp can pollute this registry, making it crucial for developers to verify the integrity of the packages they use.
