Malicious Code Injection in siska-serimuka26-pore Package - npm Vulnerability

siska-serimuka26-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98364: Malicious code in siska-serimuka26-pore (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 siska-serimuka26-pore package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making the package a target for malicious activities.

Vulnerability Detail

The vulnerability in the siska-serimuka26-pore package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior can pollute the npm registry, making it difficult for developers to trust the integrity of packages and potentially exposing them to further security risks.

How To Fix

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

npm uninstall siska-serimuka26-pore

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 avoid using the siska-serimuka26-pore package and replace it with a trusted alternative. Always verify the integrity of packages before installation.

Conclusion

The siska-serimuka26-pore package poses a significant risk due to its malicious code that alters package metadata and pollutes the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the integrity of your applications.

See every vulnerability recorded for siska-serimuka26-pore →

Share this vulnerability

FAQ

The siska-serimuka26-pore package is an npm package associated with the tea.xyz token reward campaign, designed to manipulate the npm registry.

The vulnerability can lead to the pollution of the npm registry, making it difficult to trust other packages and potentially exposing your application to further security risks.

If you have installed the siska-serimuka26-pore package, you should uninstall it immediately using 'npm uninstall siska-serimuka26-pore'.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.

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

How To Fix

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

npm uninstall siska-serimuka26-pore

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