Malicious Code Injection in joko-miebogor13-pore Package
Summary
MAL-2025-97975: Malicious code in joko-miebogor13-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
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 joko-miebogor13-pore package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. It includes scripts that automatically publish variants with altered metadata, potentially compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the joko-miebogor13-pore package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the pollution of the npm registry with numerous derivative packages, which can confuse developers and lead to security risks in applications that inadvertently depend on these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-miebogor13-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, avoid using the joko-miebogor13-pore package and any other packages that may have been published as part of the same malicious campaign. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The joko-miebogor13-pore package poses a significant risk due to its malicious behavior of altering package metadata and flooding the npm registry with derivative packages. It is crucial for developers to remove this package and regularly audit their dependencies to maintain the security of their applications.
See every vulnerability recorded for joko-miebogor13-pore →
FAQ
The impact includes potential security risks from using malicious packages and the pollution of the npm registry, which can lead to confusion and compromised applications.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without any signup.
You should immediately uninstall the joko-miebogor13-pore package and review your dependencies for any other potentially malicious packages.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your dependencies.
Regularly audit your dependencies, keep them updated, and avoid using packages from untrusted sources to minimize security risks.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
