Malicious Code Injection in vida-serimuka52-pore: A Threat to npm Ecosystem

vida-serimuka52-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98487: Malicious code in vida-serimuka52-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package vida-serimuka52-pore is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. Its primary function is to generate and publish derivative packages, but it has been compromised to include harmful scripts that can affect developers' reputations and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in vida-serimuka52-pore originates from its design to automatically publish derivative packages with randomized names. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. This can result in developers unintentionally using compromised packages, which can further propagate malicious code across projects.

How To Fix

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

npm uninstall vida-serimuka52-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 vida-serimuka52-pore package and look for alternative packages that provide similar functionality without the associated risks. Always validate the integrity of packages before including them in your project.

Conclusion

The vida-serimuka52-pore package poses a significant risk to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities to maintain the security and integrity of their applications.

See every vulnerability recorded for vida-serimuka52-pore →

Share this vulnerability

FAQ

vida-serimuka52-pore is an npm package that has been identified as malicious, designed to manipulate package publishing and inflate developer reputation scores.

If your project uses the vida-serimuka52-pore package, it may inadvertently include malicious code that can compromise your application's security and integrity.

You should immediately uninstall the package using 'npm uninstall vida-serimuka52-pore' and review your project for any potential impacts.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall vida-serimuka52-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