Malicious Code Injection in iejfaa-devapp: npm Package Vulnerability
Summary
MAL-2025-103942: Malicious code in iejfaa-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
iejfaa-devapp is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm ecosystem.
Vulnerability Detail
The vulnerability in iejfaa-devapp is rooted in its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants of the package to pollute the npm registry, which can lead to significant security risks, including the potential for dependency confusion and the introduction of further malicious packages into projects that rely on this ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall iejfaa-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 avoid using the iejfaa-devapp package until a secure version is released. Additionally, you can monitor your package-lock.json file for any unauthorized changes that may indicate the presence of this malicious package.
Conclusion
The iejfaa-devapp package has been identified as containing malicious code that compromises the integrity of the npm ecosystem. It is crucial for developers to remain vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can help safeguard your projects against potential threats.
See every vulnerability recorded for iejfaa-devapp →
FAQ
The vulnerability involves malicious code that modifies package.json to remove private flags and generates random package names, leading to pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Using this package can lead to dependency confusion, introduction of further malicious packages, and compromise of your project's security.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and avoid using unverified packages from the npm registry.
If no patched version is available, consider removing the package from your project and looking for alternative solutions that do not pose a security risk.
