Malicious Code Injection in siska-bubursumsum2-miaww Package

siska-bubursumsum2-miaww Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90611: Malicious code in siska-bubursumsum2-miaww (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 siska-bubursumsum2-miaww package is part of the npm ecosystem, primarily used for JavaScript development. It has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the siska-bubursumsum2-miaww package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of variants. The result is pollution of the npm registry and potential security risks for developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall siska-bubursumsum2-miaww

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, avoid using the siska-bubursumsum2-miaww package and monitor your project's dependencies for any malicious packages. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json file.

Conclusion

The siska-bubursumsum2-miaww package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.

See every vulnerability recorded for siska-bubursumsum2-miaww →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

Using this package can lead to security risks, including the potential for your project to be associated with malicious activities and the pollution of your dependency tree.

You should uninstall the siska-bubursumsum2-miaww package immediately and check for any other potentially malicious packages in your project.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring any signup.

How To Fix

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

npm uninstall siska-bubursumsum2-miaww

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