Critical Malicious Code Vulnerability in dsfserewkbc Package

dsfserewkbc Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18934: Malicious code in dsfserewkbc (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 dsfserewkbc package is an npm library that is designed for specific functionalities within JavaScript applications. It is utilized by developers to streamline certain processes in their projects. However, this package has been identified to contain malicious code, posing significant risks to applications that depend on it. The presence of such code can lead to unauthorized access, data breaches, and other security issues.

Vulnerability Detail

The vulnerability in the dsfserewkbc package stems from the inclusion of malicious code that can execute harmful actions within the user's environment. This code was introduced in version 0 and has the potential to compromise the integrity of applications using this package. The ramifications of this vulnerability include unauthorized data access, potential data loss, and exploitation of the affected systems by malicious actors.

How To Fix

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

npm uninstall dsfserewkbc

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 replace the dsfserewkbc package with an alternative library that offers similar functionality without the associated risks. Review your project's dependencies and consider using well-maintained and trusted packages.

Conclusion

The dsfserewkbc package has been identified as containing malicious code, posing significant risks to applications that utilize it. It is essential for developers to take immediate action by uninstalling the package and seeking alternatives or waiting for a secure version. Regular monitoring of dependencies is crucial to maintain application security.

See every vulnerability recorded for dsfserewkbc →

Share this vulnerability

FAQ

The dsfserewkbc package is an npm library used in JavaScript applications for specific functionalities, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected by this vulnerability.

If you are using dsfserewkbc, you should uninstall it immediately and look for alternative packages or wait for a patched version to be released.

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

Using a compromised package can lead to unauthorized access to sensitive data, exploitation of your application, and potential damage to your system's integrity.

How To Fix

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

npm uninstall dsfserewkbc

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