Malicious Code Injection in kupai-lukta-igafu: A Threat to npm Users
Summary
MAL-2025-157879: Malicious code in kupai-lukta-igafu (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'kupai-lukta-igafu' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating numerous derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores for token rewards, but they also pose significant security risks due to their malicious payloads.
Vulnerability Detail
The vulnerability in 'kupai-lukta-igafu' originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kupai-lukta-igafuIf 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 'kupai-lukta-igafu' package from your project by executing 'npm uninstall kupai-lukta-igafu'. This will prevent the malicious code from executing while you seek a more permanent solution.
Conclusion
The 'kupai-lukta-igafu' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to take immediate action by updating or removing the package to safeguard their applications and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for kupai-lukta-igafu →
FAQ
The primary threat is the malicious code that modifies package.json files and republishes variants, which can compromise the integrity of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If an immediate update is not possible, consider uninstalling the package to prevent any potential exploitation of the vulnerability.
While specific exploits have not been detailed, the behavior of the package suggests it could lead to further security issues within the npm ecosystem.
Regularly check for updates from trusted sources, use tools like Vulert for monitoring, and follow security advisories related to npm packages.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
