Malicious Code Injection in inal-poke37: A Threat to npm Ecosystem
Summary
MAL-2025-156423: Malicious code in inal-poke37 (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-poke37' 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 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-poke37' stems from its malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to continuously republish variants of the package to pollute the npm registry, potentially leading to reputation damage for developers and security risks for users who unknowingly install these packages. The origin of this vulnerability is linked to a broader campaign exploiting the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inal-poke37If 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-poke37' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.
Conclusion
The 'inal-poke37' package poses a significant risk due to its malicious code that alters package metadata and repackages itself. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert. Staying informed and vigilant can help mitigate risks associated with open-source packages.
See every vulnerability recorded for inal-poke37 →
FAQ
The main threat is the malicious code that modifies package metadata and repackages itself, which can lead to security vulnerabilities and reputation damage for developers.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using the command 'npm uninstall inal-poke37' and look for secure alternatives.
Yes, you should search the npm registry for similar packages that have good reviews and a solid reputation to ensure security.
Regularly audit your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
