Malicious Code Injection in inal-poke63: A Threat to npm Ecosystem
Summary
MAL-2025-156452: Malicious code in inal-poke63 (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-poke63' 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 often contain scripts that manipulate package metadata and publish derivative packages to inflate developer reputation scores, posing a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'inal-poke63' originates from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of applications that depend on these packages. The malicious payload can affect the reputation of developers and the overall security of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inal-poke63If 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 'inal-poke63' package and replace it with a trusted alternative. Always verify the integrity and source of packages before including them in your project.
Conclusion
The 'inal-poke63' package poses a significant risk due to its malicious code that manipulates package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and utilize tools like Vulert to monitor for vulnerabilities in their projects. Staying vigilant and regularly updating dependencies will help maintain the security of your applications.
See every vulnerability recorded for inal-poke63 →
FAQ
The malicious code can lead to unauthorized modifications of your project's package.json, potentially compromising your application's integrity and security.
You can check your package.json and package-lock.json files for any references to 'inal-poke63' or use tools like Vulert to monitor for vulnerabilities.
There is no patch for 'inal-poke63' as it is recommended to remove the package entirely from your project.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities, ensuring that you stay informed about potential threats.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
