Malicious Code Injection in ida-teh49-breki: A Threat to npm Users

ida-teh49-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73463: Malicious code in ida-teh49-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 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 package 'ida-teh49-breki' is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant risks to users who may unknowingly install these compromised packages.

Vulnerability Detail

The vulnerability in 'ida-teh49-breki' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of compromised software by unsuspecting developers. The malicious payload can compromise the integrity of applications relying on this package, leading to security breaches and data leaks.

How To Fix

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

npm uninstall ida-teh49-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, avoid using the 'ida-teh49-breki' package and monitor your package-lock.json for any unauthorized changes. You can also utilize tools like Vulert to monitor your dependencies for vulnerabilities in real-time.

Conclusion

The 'ida-teh49-breki' package poses a significant threat to npm users due to its malicious behavior aimed at inflating developer reputation scores. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to ensure the security of your applications.

See every vulnerability recorded for ida-teh49-breki →

Share this vulnerability

FAQ

The 'ida-teh49-breki' package is a malicious npm package that is part of a campaign to inflate developer reputation scores by generating numerous derivative packages.

This vulnerability can lead to the installation of compromised software, potentially resulting in security breaches and data leaks within your application.

You should uninstall the 'ida-teh49-breki' package immediately using the command 'npm uninstall ida-teh49-breki'.

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

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

How To Fix

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

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