Malicious Code Injection in inal-poke106: A Threat to npm Ecosystem
Summary
MAL-2025-156379: Malicious code in inal-poke106 (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-poke106' is part of the npm ecosystem, which is widely used for JavaScript package management. This specific package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks for users and developers relying on npm packages.
Vulnerability Detail
The vulnerability in 'inal-poke106' originates from its association with a token reward campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with altered metadata. The malicious payload modifies the package.json file to remove private flags, changes version numbers, and creates random package names, ultimately leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, which may contain harmful code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inal-poke106If 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 'inal-poke106' and any other packages that are part of the malicious campaign. Regularly audit your project's dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The 'inal-poke106' package poses a significant security risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their applications from potential threats.
See every vulnerability recorded for inal-poke106 →
FAQ
Using the inal-poke106 package can lead to the introduction of malicious code into your application, compromising its security and potentially affecting users.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By uploading your package-lock.json file, you can check for vulnerabilities without needing to access the code.
If you have installed inal-poke106, you should uninstall it immediately using 'npm uninstall inal-poke106' and review your project's dependencies for any other potentially compromised packages.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.
To avoid vulnerabilities, always use trusted packages, regularly update dependencies, and conduct security audits on your project.
