Malicious Code Injection in inal-poke67: A Threat to npm Ecosystem
Summary
MAL-2025-156456: Malicious code in inal-poke67 (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-poke67' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'inal-poke67' stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants, which pollutes the npm registry and can potentially harm developers and users relying on legitimate packages. The malicious code is part of a broader scheme to exploit the npm ecosystem for token rewards, making it a significant concern for developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inal-poke67If 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-poke67' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages to ensure that no malicious packages are present.
Conclusion
The 'inal-poke67' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing harmful variants. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.
See every vulnerability recorded for inal-poke67 →
FAQ
The primary risk is that it modifies your package.json file and repopulates the npm registry with malicious packages, potentially compromising your project's integrity.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Immediately uninstall the package using 'npm uninstall inal-poke67' and check your package-lock.json for any lingering references.
Currently, there are no specific patches for 'inal-poke67'. The best course of action is to remove the package entirely.
Regularly audit your npm packages, use trusted sources, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
