Malicious Code Vulnerability in ida-ketoprak60-breki Package

ida-ketoprak60-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73434: Malicious code in ida-ketoprak60-breki (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The ida-ketoprak60-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publishing of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the integrity of the npm registry.

Vulnerability Detail

The vulnerability stems from the package's malicious payload, which 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, effectively polluting the npm registry and potentially compromising other packages and developers' reputations. The origin of this vulnerability is linked to the broader issue of malicious packages flooding the npm ecosystem, specifically targeting the tea protocol token reward system.

How To Fix

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

npm uninstall ida-ketoprak60-breki

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 ida-ketoprak60-breki package and any packages that depend on it. Additionally, consider using a package-lock.json file to monitor your dependencies and ensure that no malicious packages are introduced into your project.

Conclusion

The ida-ketoprak60-breki package contains a significant vulnerability that can compromise the integrity of your project and the npm registry. It is crucial to remove this package and monitor your dependencies for any malicious activity. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities in your open-source projects.

See every vulnerability recorded for ida-ketoprak60-breki →

Share this vulnerability

FAQ

The ida-ketoprak60-breki package is an npm package associated with the tea.xyz token reward campaign, designed to automatically generate and publish derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising your project's integrity and affecting your developer reputation.

You should uninstall the ida-ketoprak60-breki package immediately and check for any other affected dependencies in your project.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

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 ida-ketoprak60-breki

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