Malicious Code Injection in eka-papeda60-pore Package: A Threat to npm Registry Integrity
Summary
MAL-2025-97738: Malicious code in eka-papeda60-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-papeda60-pore package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores through token rewards.
Vulnerability Detail
The vulnerability in the eka-papeda60-pore package originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The scripts continuously republish these variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The ramifications include the risk of developers unknowingly using compromised packages, which can lead to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eka-papeda60-poreIf 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, avoid using the eka-papeda60-pore package and any other packages that may be associated with the tea.xyz campaign. Monitor your project's dependencies closely and consider using tools like Vulert to check for vulnerabilities in your package-lock.json file. You can use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without any signup.
Conclusion
The eka-papeda60-pore package poses a significant risk due to its malicious code that can compromise the npm registry. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor their dependencies for vulnerabilities. By taking proactive measures, developers can safeguard their applications against potential threats.
See every vulnerability recorded for eka-papeda60-pore →
FAQ
The eka-papeda60-pore package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the use of compromised packages, which may introduce security risks and affect the integrity of your application.
You should uninstall the eka-papeda60-pore package immediately and check your project for any other potentially compromised packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without requiring any signup.
