Critical Malicious Code Vulnerability in nokaca Package
Summary
MAL-2025-192848: Malicious code in nokaca (npm). Affects nokaca versions 1.0.0 – 1.0.1. 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 nokaca package is a JavaScript library available on npm, designed to facilitate specific functionalities within Node.js applications. It is widely used for its ease of integration and lightweight nature. However, recent findings have revealed that certain versions of this package contain malicious code, posing a significant security risk to applications that utilize it.
Vulnerability Detail
The vulnerability in the nokaca package stems from the introduction of malicious code in versions 1.0.0 and 1.0.1. This code can potentially compromise the integrity of applications, leading to unauthorized access, data breaches, or other malicious activities. The issue was identified by ReversingLabs and is documented in their findings. The affected versions are known to execute harmful operations that can affect the overall security posture of any application relying on them.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokacaIf 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
If immediate updating is not feasible, consider removing the nokaca package from your project until a secure version is confirmed. You can do this by running:
npm uninstall nokaca
This will help mitigate the risk while you assess alternative solutions or wait for a patch.
Conclusion
The discovery of malicious code in the nokaca package highlights the importance of regularly updating dependencies and monitoring for vulnerabilities. By following the recommended steps to update or uninstall the affected package, developers can protect their applications from potential threats.
See every vulnerability recorded for nokaca →
FAQ
Versions 1.0.0 and 1.0.1 of the nokaca package are affected by the malicious code vulnerability.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
Using the affected versions can lead to unauthorized access, data breaches, and other malicious activities that compromise application security.
Yes, you can temporarily uninstall the nokaca package until a secure version is available.
The vulnerability was identified by ReversingLabs, a cybersecurity firm specializing in threat detection.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
