Malicious Code Injection in inal-poke34: A Threat to npm Ecosystem
Summary
MAL-2025-156420: Malicious code in inal-poke34 (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
inal-poke34 is an npm package that is part of a broader campaign aimed at exploiting the npm registry. It is designed to facilitate token reward schemes by automatically generating and publishing derivative packages. This package, like others in the campaign, has been identified as containing malicious scripts that can compromise the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in inal-poke34 stems from its inclusion in a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This behavior not only inflates developer reputation scores but also leads to the pollution of the npm registry with potentially harmful packages. The malicious payload can result in unintended consequences for developers who may unknowingly install these compromised packages, leading to security risks and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inal-poke34If 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-poke34 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly check your package-lock.json for any dependencies that may have been affected by this vulnerability.
Conclusion
The inal-poke34 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with harmful variants. It is crucial for developers to remove this package and remain vigilant about their dependencies to maintain the integrity of their applications.
See every vulnerability recorded for inal-poke34 →
FAQ
The inal-poke34 package contains malicious code that modifies package.json files and publishes harmful variants to the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed the inal-poke34 package, you should uninstall it immediately using npm uninstall inal-poke34 and audit your dependencies for any other vulnerabilities.
Yes, consider using alternative packages that provide similar functionality but are verified to be safe and free from malicious code.
Regularly audit your dependencies, use trusted sources for packages, and consider implementing tools like Vulert to monitor for vulnerabilities in real-time.
