Malicious Code Injection in inal-poke40: A Threat to npm Ecosystem
Summary
MAL-2025-156427: Malicious code in inal-poke40 (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-poke40' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages typically contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'inal-poke40' stems from 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 pollute the npm registry by continuously republishing variants, which can lead to confusion, potential security risks, and a degradation of trust in the npm ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits the npm platform for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inal-poke40If 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 this malicious package by using npm's package-lock.json file to monitor and restrict the installation of known vulnerable packages. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The 'inal-poke40' package poses a significant risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.
See every vulnerability recorded for inal-poke40 →
FAQ
The malicious code can lead to the modification of your project's package.json, potentially exposing your project to further vulnerabilities and affecting the integrity of your application.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If you have installed 'inal-poke40', it is recommended to remove it immediately and check for any other affected packages in your project.
Yes, Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with the latest security advisories for the packages you use.
