Malicious Code Injection in okta-tempe64-pore: A Threat to npm Packages
Summary
MAL-2025-98221: Malicious code in okta-tempe64-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 package 'okta-tempe64-pore' 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 of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can harm developers' reputations and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in 'okta-tempe64-pore' originates from its association with a token reward campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious activity modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly integrate these compromised packages into their applications, as well as damage to 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 okta-tempe64-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 avoid using the 'okta-tempe64-pore' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.
Conclusion
The 'okta-tempe64-pore' package poses a significant risk due to its malicious code aimed at manipulating the npm registry. Developers are advised to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for okta-tempe64-pore →
FAQ
The malicious code can lead to the pollution of the npm registry and may compromise the security of applications that use this package.
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.
Remove the package from your project and consider updating to a patched version if available. Also, audit your dependencies for any other vulnerabilities.
Regularly audit your dependencies using tools like npm audit and stay informed about vulnerabilities in the packages you use.
If you face issues, check for alternative packages that provide similar functionality and ensure your application is thoroughly tested after making changes.
