Malicious Code Injection in ida-keraktelor74-breki: A Threat to npm Packages

ida-keraktelor74-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73431: Malicious code in ida-keraktelor74-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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'ida-keraktelor74-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to generate and publish derivative packages with randomized names, which can lead to reputation inflation for developers involved in the tea.xyz token reward campaign.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the 'ida-keraktelor74-breki' package. This code modifies the package.json file by removing private flags, altering version numbers, and creating random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to security risks for developers and users who may inadvertently install these compromised packages. The malicious payload can also affect the integrity of the npm ecosystem by making it difficult to trust legitimate packages.

How To Fix

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

npm uninstall ida-keraktelor74-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-keraktelor74-breki' package and any packages that depend on it. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.

Conclusion

The 'ida-keraktelor74-breki' package poses a significant threat due to its malicious code designed to exploit the npm ecosystem. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive steps can help maintain the security and integrity of software projects.

See every vulnerability recorded for ida-keraktelor74-breki →

Share this vulnerability

FAQ

It is an npm package identified as part of a malicious campaign that exploits the npm publishing system.

The vulnerability can lead to the installation of malicious code, which may compromise the security and integrity of your project.

You should uninstall the package immediately using 'npm uninstall ida-keraktelor74-breki' and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall ida-keraktelor74-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