Malicious Code Injection in okta-kripik33-miaww: A Threat to npm Packages
Summary
MAL-2025-89166: Malicious code in okta-kripik33-miaww (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 package 'okta-kripik33-miaww' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'okta-kripik33-miaww' originates 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 leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications relying on these packages. The malicious payload can potentially allow unauthorized access or manipulation of the application using this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall okta-kripik33-miawwIf 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 the following command to uninstall it: npm uninstall okta-kripik33-miaww. Additionally, consider using npm audit to identify and address other vulnerabilities in your project.
Conclusion
The 'okta-kripik33-miaww' package poses a significant security threat due to its malicious code designed to manipulate package metadata. It is essential to remove this package and monitor your project for vulnerabilities using tools like Vulert. Staying informed and proactive can help safeguard your applications from similar threats.
See every vulnerability recorded for okta-kripik33-miaww →
FAQ
The malicious code can lead to unauthorized modifications of your package.json file, potentially compromising your application's security and integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed 'okta-kripik33-miaww', it is crucial to uninstall it immediately and check for any other vulnerabilities in your project.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities by analyzing your package-lock.json file.
Regularly audit your dependencies using npm audit, keep your packages updated, and utilize tools like Vulert for real-time monitoring.
