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

ida-getuk36-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73429: Malicious code in ida-getuk36-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 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 package 'ida-getuk36-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with random names. The primary functionality of these packages is to inflate developer reputation scores for rewards associated with the tea protocol. However, they pose significant risks due to their malicious payloads.

Vulnerability Detail

The vulnerability in 'ida-getuk36-breki' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall ida-getuk36-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 measure, you can avoid using the affected package and monitor your dependencies for any malicious activity. Consider using tools like Vulert, which can help you monitor and alert for open-source vulnerabilities in your software without requiring access to the code or installation. You can also check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.

Conclusion

The 'ida-getuk36-breki' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant about their dependencies and take proactive measures to secure their applications against such vulnerabilities.

See every vulnerability recorded for ida-getuk36-breki →

Share this vulnerability

FAQ

'ida-getuk36-breki' is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

This vulnerability can lead to the inclusion of compromised packages in your project, which may introduce security risks and undermine the integrity of your application.

You should uninstall the package immediately using 'npm uninstall ida-getuk36-breki' and review your other dependencies for potential vulnerabilities.

Regularly update your dependencies, use trusted packages, and employ monitoring tools like Vulert to keep track of vulnerabilities in your software.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this or other vulnerabilities.

How To Fix

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

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