Malicious Code Injection in joko-gulai6-pore Package: npm Vulnerability Overview
Summary
MAL-2025-97970: Malicious code in joko-gulai6-pore (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 joko-gulai6-pore package is part of the npm ecosystem, primarily used for JavaScript development. It has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant issues in the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the joko-gulai6-pore package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This behavior not only compromises the security of the affected packages but also affects the overall trustworthiness of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-gulai6-poreIf 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 prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include the joko-gulai6-pore package by removing it from your package.json file and running npm install.
Conclusion
The joko-gulai6-pore package presents a significant security risk due to its malicious code designed to manipulate npm registry integrity. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for joko-gulai6-pore →
FAQ
The vulnerability can lead to the proliferation of malicious packages in the npm registry, compromising the integrity of the ecosystem and potentially affecting other projects that depend on these packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities. You can check your application against this vulnerability using the Vulert playground at Vulert Scanner.
If you cannot update the package, consider removing it from your project and replacing it with a secure alternative to mitigate the risk.
The malicious payload modifies the package.json file to remove private flags, changes version numbers, and generates random package names, allowing it to republish variants that can mislead developers.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
