Malicious Code Injection in eka-empal52-pore Package - npm Vulnerability
Summary
MAL-2025-97732: Malicious code in eka-empal52-pore (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 eka-empal52-pore package is part of the tea.xyz token reward campaign that has recently infiltrated the npm ecosystem. This package, like others in the campaign, is designed to automate the generation and publication of derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but this leads to significant risks for users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the eka-empal52-pore package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This behavior not only compromises the security of applications using this package but also undermines the trustworthiness of the npm ecosystem as a whole. The malicious payload is designed to continuously republish variants, exacerbating the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eka-empal52-pore
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 prevent the installation of the eka-empal52-pore package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include this package and regularly audit your dependencies for any malicious packages.
Conclusion
The eka-empal52-pore package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your project and monitor your dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for eka-empal52-pore →
FAQ
The eka-empal52-pore package is part of a campaign that aims to inflate developer reputation scores by flooding the npm registry with malicious packages.
The vulnerability can lead to the modification of your package.json file, potentially compromising your application's integrity and security.
You should uninstall the eka-empal52-pore package immediately and audit your project for any other malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for any open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.