Malicious Code Detected in dsfserewkbaaai Package - Security Alert

dsfserewkbaaai Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18869: Malicious code in dsfserewkbaaai (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The dsfserewkbaaai package is an npm library that has been identified to contain malicious code. This package may be used in various JavaScript applications to provide specific functionalities, but its integrity has been compromised, posing a significant risk to users and developers who integrate it into their projects.

Vulnerability Detail

The vulnerability in the dsfserewkbaaai package stems from the inclusion of malicious code that can execute harmful actions on the user's system. This code can lead to data breaches, unauthorized access, and other security threats. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall dsfserewkbaaai

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

Conclusion

The dsfserewkbaaai package has been identified as containing malicious code, posing serious security risks to users. Immediate action is required to uninstall the package and seek alternatives. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for dsfserewkbaaai →

Share this vulnerability

FAQ

The dsfserewkbaaai package is an npm library that has been found to contain malicious code, posing security risks to applications that use it.

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 any signup.

If you have installed the dsfserewkbaaai package, you should uninstall it immediately using 'npm uninstall dsfserewkbaaai' and look for alternative packages.

Currently, there is no patch available for the dsfserewkbaaai package. Users are advised to uninstall the package until a secure version is released.

Using the dsfserewkbaaai package can lead to data breaches, unauthorized access to sensitive information, and other significant security threats.

How To Fix

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

npm uninstall dsfserewkbaaai

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