Critical Malicious Code Vulnerability in dsfserewkbaaam Package

dsfserewkbaaam Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18873: Malicious code in dsfserewkbaaam (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 dsfserewkbaaam package is an npm library that is designed to provide specific functionalities for developers. However, it has been identified as containing malicious code, which poses a significant risk to applications that utilize this package. The presence of such code can lead to unauthorized access, data breaches, and other security issues.

Vulnerability Detail

The vulnerability in the dsfserewkbaaam package stems from the inclusion of malicious code that was intentionally embedded by the package maintainers. This code can execute harmful actions within the user's environment, potentially compromising sensitive data and system integrity. The vulnerability was introduced in version 0 and affects all subsequent versions, making it critical for users to address it immediately.

How To Fix

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

npm uninstall dsfserewkbaaam

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 dsfserewkbaaam package altogether until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The dsfserewkbaaam package contains malicious code that poses a serious threat to applications. It is crucial for developers to uninstall this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for dsfserewkbaaam →

Share this vulnerability

FAQ

The dsfserewkbaaam package is an npm library used for specific functionalities in JavaScript applications.

The malicious code was identified through security assessments conducted by Amazon Inspector.

Using this package can lead to unauthorized access, data breaches, and potential damage to your application's integrity.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall dsfserewkbaaam

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