Malicious Code Injection in inal-poke11: A Threat to npm Ecosystem
Summary
MAL-2025-156383: Malicious code in inal-poke11 (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-poke11' is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate npm's publishing system, generating numerous derivative packages with the intent to inflate developer reputation scores. It operates by modifying package metadata and continuously republishing variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'inal-poke11' originates from its malicious code, which alters the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages. The malicious payload can lead to reputation damage and potential security risks for applications relying on affected packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inal-poke11If 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 package by using npm's package-lock.json to monitor dependencies. You can also utilize the following command to uninstall the package: npm uninstall inal-poke11.
Conclusion
The 'inal-poke11' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and proliferates compromised packages. It is essential for developers to remove this package and monitor their dependencies regularly to ensure application security.
See every vulnerability recorded for inal-poke11 →
FAQ
The primary risk is the injection of malicious code that alters package metadata and can lead to the proliferation of compromised packages in the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json, it can help identify affected packages.
You should immediately uninstall the package using 'npm uninstall inal-poke11' and check for any other dependencies that may have been affected.
Regularly audit your dependencies using tools like Vulert and keep your packages updated to the latest secure versions to minimize risks.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
