Critical Malicious Code Vulnerability in okta-template-validator Package

okta-template-validator Updated 02 Oct 2025

Summary

15/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5944: Malicious code in okta-template-validator (npm). Affects okta-template-validator versions 99.99.99. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The okta-template-validator is an npm package designed to assist developers in validating Okta templates. It is widely used in applications that integrate with Okta for authentication and authorization. However, this package has been found to contain malicious code, posing a significant security risk to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the okta-template-validator package. This code can compromise any computer on which the package is installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to full system compromise, making it crucial for users to take immediate action.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall okta-template-validator

If 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 workaround, you can temporarily disable the usage of the okta-template-validator package in your application while you assess the impact and remove it. Ensure that you do not run any applications that depend on this package until it has been completely removed.

Conclusion

The okta-template-validator package has been identified as containing malicious code that poses a critical security risk. Immediate action is required to remove the package and secure any affected systems. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for okta-template-validator →

Share this vulnerability

FAQ

You should immediately remove the package and rotate any secrets or keys stored on the affected computer.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Failure to address this vulnerability can lead to unauthorized access to sensitive data and complete system compromise.

It is highly discouraged to continue using your application until the okta-template-validator package has been removed and the system has been secured.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall okta-template-validator

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback