Critical Malicious Code Vulnerability in dsfserewkb Package

dsfserewkb Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18854: Malicious code in dsfserewkb (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 dsfserewkb package is an npm module designed for various functionalities within JavaScript applications. It is utilized by developers for its ease of integration and lightweight nature. However, this package has been identified to contain malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the dsfserewkb package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The vulnerability was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall dsfserewkb

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 prevent the use of the dsfserewkb package in your application by removing it from your package.json file and running the command: npm uninstall dsfserewkb. This will help mitigate the risk until a secure alternative is found.

Conclusion

The dsfserewkb package has been identified as containing malicious code, posing a serious threat to applications that utilize it. Immediate action is required to remove the package and mitigate potential risks. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in the future.

See every vulnerability recorded for dsfserewkb →

Share this vulnerability

FAQ

The dsfserewkb package is an npm module used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can help you identify if your application is affected by this vulnerability.

If you are using dsfserewkb, it is crucial to uninstall the package immediately and look for a secure alternative to avoid potential security risks.

Currently, there is no patched version available for the dsfserewkb package. It is recommended to remove the package entirely.

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 dsfserewkb

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