Malicious Code Injection in okta-tumis29-pore Package

okta-tumis29-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98222: Malicious code in okta-tumis29-pore (npm). Affected versions are not published. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The okta-tumis29-pore package is part of the npm ecosystem, often utilized for various JavaScript applications. However, it has been identified as a malicious package linked to the tea.xyz token reward campaign, which aims to manipulate npm's reputation system. This package is designed to automatically generate and publish derivative packages with randomized names, compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious intent to modify the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This behavior not only affects developers' reputations but also poses security risks by introducing potentially harmful code into projects that depend on these packages.

How To Fix

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

npm uninstall okta-tumis29-pore

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 temporary workaround, you can avoid using the okta-tumis29-pore package and replace it with a trusted alternative that provides similar functionality. Additionally, regularly audit your dependencies using tools like Vulert to monitor for vulnerabilities.

Conclusion

The okta-tumis29-pore package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for okta-tumis29-pore →

Share this vulnerability

FAQ

The okta-tumis29-pore package is an npm package that has been identified as malicious, designed to manipulate the npm registry for token rewards.

This vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and affecting the integrity of your application.

If you have installed the okta-tumis29-pore package, you should uninstall it immediately and check for any dependencies that may be affected.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall okta-tumis29-pore

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