Malicious Code Injection in iwan-tempe64-breki: A Threat to npm Ecosystem

iwan-tempe64-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73608: Malicious code in iwan-tempe64-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'iwan-tempe64-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant security risk to developers and their applications.

Vulnerability Detail

The vulnerability in 'iwan-tempe64-breki' originates from its malicious intent to modify the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into their applications.

How To Fix

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

npm uninstall iwan-tempe64-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

Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package. Ensure to monitor your dependencies regularly and avoid using packages with suspicious origins.

Conclusion

The 'iwan-tempe64-breki' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and flooding the registry with unwanted packages. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity and security of their applications.

See every vulnerability recorded for iwan-tempe64-breki →

Share this vulnerability

FAQ

The main risk is that it modifies your package.json file, potentially introducing vulnerabilities and cluttering the npm registry with malicious packages.

You can use Vulert, which monitors open-source vulnerabilities in your software. By simply using your package-lock.json file, you can check for vulnerabilities without any installation.

You should uninstall the package immediately using 'npm uninstall iwan-tempe64-breki' to prevent any potential security risks.

As of now, there are no patched versions available. It is recommended to remove the package until a secure version is released.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by vulnerabilities without needing to sign up.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall iwan-tempe64-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