Malicious Code Injection in ida-tongseng2-breki Package

ida-tongseng2-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73467: Malicious code in ida-tongseng2-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 ida-tongseng2-breki package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, aimed at inflating developer reputation scores for token rewards. This package, like others in the campaign, contains scripts that automatically publish variants with altered metadata.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the package, which modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior not only pollutes the npm registry but can also lead to security risks for developers who inadvertently use these compromised packages. The malicious payload can potentially allow attackers to execute arbitrary code or manipulate project dependencies.

How To Fix

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

npm uninstall ida-tongseng2-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 use the following command to prevent the installation of this malicious package: 'npm install --no-optional'. However, the best practice is to remove the package entirely.

Conclusion

The ida-tongseng2-breki package poses a significant security risk due to its malicious code that alters project metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies regularly to maintain the integrity of their projects.

See every vulnerability recorded for ida-tongseng2-breki →

Share this vulnerability

FAQ

ida-tongseng2-breki is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

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

You should uninstall the ida-tongseng2-breki package immediately and check for any dependencies that may be affected.

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 by this vulnerability without signing up.

How To Fix

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

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