Malicious Code Exploit in joknmax Package: npm Vulnerability Overview
Summary
MAL-2025-97965: Malicious code in joknmax (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 joknmax package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and sharing of code within the JavaScript community. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities to inflate developer reputation scores through automated scripts.
Vulnerability Detail
The vulnerability in the joknmax package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to continuously republish variants of the package, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has led to the proliferation of such malicious packages in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joknmaxIf 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 joknmax package and any other packages that may have been published as part of the same malicious campaign. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The joknmax package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their projects. Regular monitoring and updating of packages can help mitigate these risks.
See every vulnerability recorded for joknmax →
FAQ
The joknmax package is a JavaScript package available on npm, which has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project by introducing malicious code through derivative packages.
You should remove the joknmax package from your project immediately and check for any other affected packages that may have been published as part of the same campaign.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
To prevent vulnerabilities, regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert for real-time monitoring.
