Malicious Code Detected in dsfserewkbaak Package - Security Alert

dsfserewkbaak Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18894: Malicious code in dsfserewkbaak (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 dsfserewkbaak package is an npm library that serves various functionalities within JavaScript applications. It is designed to facilitate developers in building and managing their projects efficiently. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the dsfserewkbaak package stems from the inclusion of malicious code that can compromise the security of applications. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability was discovered by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security flaws.

How To Fix

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

npm uninstall dsfserewkbaak

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, consider replacing the dsfserewkbaak package with an alternative library that provides similar functionality without the associated risks. Review your project's dependencies and assess other npm packages that can fulfill your requirements safely.

Conclusion

The dsfserewkbaak package has been flagged for containing malicious code, posing serious security risks to applications. It is essential to take immediate action by removing the package and considering alternatives. Regularly monitoring your dependencies with tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for dsfserewkbaak →

Share this vulnerability

FAQ

The dsfserewkbaak package is an npm library used in JavaScript applications for various functionalities.

The malicious code was identified by Amazon Inspector, a security tool that scans for vulnerabilities in open-source packages.

Using the dsfserewkbaak package can lead to unauthorized access, data breaches, and other security threats to your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

If no patched version is available, it is recommended to remove the package entirely and seek alternative libraries that provide similar functionality.

How To Fix

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

npm uninstall dsfserewkbaak

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