Malicious Code Detected in dsfserewkbaad Package - Security Alert

dsfserewkbaad Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18887: Malicious code in dsfserewkbaad (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 dsfserewkbaad package is an npm library that serves various functionalities within JavaScript applications. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. This vulnerability can lead to unauthorized access, data breaches, and potential exploitation of the affected systems.

Vulnerability Detail

The dsfserewkbaad package has been found to harbor malicious code that can compromise the security of applications using it. This vulnerability originated from the package itself, which was introduced in version 0 and has not been addressed. The ramifications of this vulnerability include unauthorized data access, potential data loss, and exploitation of the application environment, which can lead to severe security incidents.

How To Fix

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

npm uninstall dsfserewkbaad

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 avoid using the dsfserewkbaad package in your application. If it is already included, remove it from your package.json file and run npm install to update your dependencies.

Conclusion

The dsfserewkbaad package has been identified as containing malicious code, posing significant security risks to applications that utilize it. Immediate action is required to remove the package and safeguard your application from potential exploitation. Regularly monitor your dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for dsfserewkbaad →

Share this vulnerability

FAQ

dsfserewkbaad is an npm package used in JavaScript applications, but it has been flagged for containing malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

You should remove the dsfserewkbaad package from your project immediately and look for alternative packages that provide similar functionality.

Currently, there is no patched version available for the dsfserewkbaad package. It is recommended to remove the package until a secure alternative is found.

Using a package with malicious code can lead to unauthorized access to sensitive data, data breaches, and exploitation of your application, which can have severe consequences for your organization.

How To Fix

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

npm uninstall dsfserewkbaad

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