Malicious Code Injection in nokire-korean1: A Threat to npm Packages
Summary
MAL-2025-162740: Malicious code in nokire-korean1 (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 'nokire-korean1' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious content.
Vulnerability Detail
The vulnerability in 'nokire-korean1' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to security risks for developers who unknowingly incorporate these packages into their projects, potentially exposing them to further vulnerabilities and malicious code execution.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-korean1If 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 measure, you can avoid using the 'nokire-korean1' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.
Conclusion
The 'nokire-korean1' package poses a significant threat due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to be vigilant about their dependencies and utilize tools like Vulert to monitor for vulnerabilities. Removing the affected package and seeking alternatives is the best course of action to ensure the security of your applications.
See every vulnerability recorded for nokire-korean1 →
FAQ
The primary risk is the potential for malicious code execution and the pollution of the npm registry, which can compromise the integrity of your application.
You can use Vulert, which monitors open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected.
You should immediately remove the package from your project and check for any alternative packages that can fulfill your requirements.
Regularly audit your dependencies using tools like Vulert and stay updated with security advisories from the npm registry.
Yes, you can report vulnerabilities to npm through their security reporting channels to help protect the community.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
