Malicious Code Injection in siska-kupat47-breki Package

siska-kupat47-breki Updated 23 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75486: Malicious code in siska-kupat47-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 siska-kupat47-breki package is part of a broader campaign associated with the tea.xyz token reward system. This npm package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to manipulate developer reputation scores. The package's functionality is compromised by malicious scripts that alter its metadata and continuously republish variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the siska-kupat47-breki package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The result is a flood of derivative packages in the npm registry, which can undermine the integrity of the ecosystem and potentially expose users to further security risks.

How To Fix

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

npm uninstall siska-kupat47-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 siska-kupat47-breki package and any packages that depend on it. Additionally, consider using npm audit to identify and address vulnerabilities in your project dependencies.

Conclusion

The siska-kupat47-breki package contains malicious code that compromises its integrity and can affect the broader npm ecosystem. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for siska-kupat47-breki →

Share this vulnerability

FAQ

siska-kupat47-breki is an npm package associated with a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.

The malicious code alters your package metadata, potentially exposing your project to further vulnerabilities and cluttering the npm registry with unwanted packages.

You should remove the siska-kupat47-breki package from your project immediately and monitor for any updates or patches.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Regularly audit your dependencies using tools like npm audit, and stay informed about the packages you include in your project.

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 siska-kupat47-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