Malicious Code Injection in inal-poke114: A Threat to npm Ecosystem
Summary
MAL-2025-156388: Malicious code in inal-poke114 (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 'inal-poke114' 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 known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate the npm registry, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'inal-poke114' originates from its design to include autopublish scripts that automatically generate and publish derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants. The result is a polluted npm registry, which can lead to reputation inflation for malicious actors and potential security risks for users who inadvertently install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inal-poke114
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 measure, avoid using the 'inal-poke114' package and monitor your project's dependencies for any similar malicious packages. You can also use tools like Vulert to scan your package-lock.json file for vulnerabilities.
Conclusion
The 'inal-poke114' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and repopulates the registry with harmful variants. It is crucial for developers to be vigilant and utilize tools like Vulert to monitor their dependencies for vulnerabilities.
See every vulnerability recorded for inal-poke114 →
FAQ
The primary risk is that it can modify your package.json file and republish malicious variants, leading to potential security breaches.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
You should uninstall the package immediately using 'npm uninstall inal-poke114' and check for any other malicious packages in your dependencies.
No, there are no patches available for this package as it is inherently malicious. It is recommended to remove it completely.
Vulert monitors your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues without needing access to your code.