Malicious Code Injection in inal-poke68: A Threat to npm Ecosystem
Summary
MAL-2025-156457: Malicious code in inal-poke68 (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-poke68' is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but this behavior poses significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'inal-poke68' originates from its malicious payload, which modifies the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a compromised development environment, increased risk of dependency confusion, and potential exploitation of developers unaware of the malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inal-poke68If 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 remove the 'inal-poke68' package from your project by executing the command: 'npm uninstall inal-poke68'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'inal-poke68' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with unwanted packages. It is crucial for developers to stay informed about such vulnerabilities and take necessary actions to protect their projects.
See every vulnerability recorded for inal-poke68 →
FAQ
The primary risk is the potential for malicious code to compromise your development environment and inflate npm registry with unwanted packages.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities. Visit Vulert Scanner to check your application without needing to sign up.
If immediate updates are not possible, consider removing the package as a temporary measure to mitigate risks.
Yes, tools like Vulert can help monitor your dependencies and alert you to vulnerabilities in real-time.
The npm registry is a critical repository for JavaScript packages, and malicious activities can undermine its integrity, affecting countless developers.
