Malicious Code Detected in dsfserewkbaaas Package - MAL-2025-18879

dsfserewkbaaas Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18879: Malicious code in dsfserewkbaaas (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 dsfserewkbaaas package is an npm library that is typically used for various functionalities within JavaScript applications. However, it has been identified as containing malicious code that poses significant security risks to applications utilizing this package. Users should be cautious as this vulnerability can lead to unauthorized access or data breaches.

Vulnerability Detail

The vulnerability in the dsfserewkbaaas package originates from the inclusion of malicious code that can compromise the security of applications. This code can execute harmful actions without the user's consent, potentially leading to data theft, unauthorized access, or system corruption. The malicious nature of this package was confirmed by security researchers, emphasizing the need for immediate action to mitigate risks.

How To Fix

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

npm uninstall dsfserewkbaaas

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 dsfserewkbaaas package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The dsfserewkbaaas package has been identified as containing malicious code, posing significant risks to applications. It is crucial to uninstall this package and consider alternatives to ensure the security of your software. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for dsfserewkbaaas →

Share this vulnerability

FAQ

dsfserewkbaaas is an npm package used in JavaScript applications, but it has been found to contain malicious code.

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

If you have installed the dsfserewkbaaas package, you should uninstall it immediately using npm uninstall dsfserewkbaaas.

Yes, you should look for alternative npm packages that provide similar functionalities without the security risks associated with dsfserewkbaaas.

You can use tools like Vulert to monitor your package-lock.json for vulnerabilities and receive alerts in real-time.

How To Fix

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

npm uninstall dsfserewkbaaas

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