Malicious Code Detected in dsfserewkbaam Package - Security Alert

dsfserewkbaam Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18896: Malicious code in dsfserewkbaam (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 dsfserewkbaam package is an npm library that serves various functionalities within JavaScript applications. It is designed to facilitate certain operations, but it has been identified as containing malicious code that poses a significant security risk to users and their applications. This vulnerability can lead to unauthorized access, data breaches, and potential exploitation of the affected systems.

Vulnerability Detail

The vulnerability in the dsfserewkbaam package originates from the inclusion of malicious code that was intentionally embedded by the package maintainers. This code can execute harmful actions on the user's system, such as stealing sensitive information or compromising application integrity. The ramifications of this vulnerability are severe, as it can lead to data loss, unauthorized access, and a breach of user trust. It is crucial for developers using this package to be aware of its malicious nature and take immediate action to mitigate the risks.

How To Fix

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

npm uninstall dsfserewkbaam

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 workaround, users can temporarily disable any functionalities that rely on the dsfserewkbaam package until a secure alternative is implemented. Additionally, monitoring tools like Vulert can be utilized to keep track of vulnerabilities in your project. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The dsfserewkbaam package has been identified as containing malicious code, posing a significant security risk to users. It is crucial to remove this package and monitor your applications for vulnerabilities using tools like Vulert. Stay informed and proactive to protect your applications from potential threats.

See every vulnerability recorded for dsfserewkbaam →

Share this vulnerability

FAQ

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

You can check if your application is affected by using the Vulert playground at Vulert Scanner.

You should remove the dsfserewkbaam package from your project and replace it with a secure alternative.

Currently, there is no patched version available for the dsfserewkbaam package. It is recommended to avoid using it.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall dsfserewkbaam

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