Malicious Code Injection in lina-poke31: A Threat to npm Packages
Summary
MAL-2025-158114: Malicious code in lina-poke31 (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
lina-poke31 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify essential files and republish itself under various names, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability in lina-poke31 originates from its design to include autopublish scripts that manipulate the package.json file. This manipulation removes private flags, alters version numbers, and generates random package names, which can lead to a polluted npm registry. The ramifications of this vulnerability include the potential for developers to unknowingly install compromised packages, leading to security breaches and the degradation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lina-poke31If 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 lina-poke31 package and monitor your project for any dependencies that may inadvertently include it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The lina-poke31 package poses a significant threat due to its malicious code designed to manipulate package metadata and republish itself. It is essential for developers to be vigilant, remove any affected packages, and utilize monitoring tools like Vulert to safeguard their projects against such vulnerabilities.
See every vulnerability recorded for lina-poke31 →
FAQ
lina-poke31 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of compromised packages, which may introduce security risks and degrade the integrity of your project's dependencies.
You should immediately remove the lina-poke31 package from your project and check for any other dependencies that may have been affected.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time, providing alerts for any issues.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
