Malicious Code Detected in dr-logger-client: A Critical Security Concern

dr-logger-client Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18724: Malicious code in dr-logger-client (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 dr-logger-client package is an npm library designed for logging client-side events in applications. It is widely used due to its simplicity and effectiveness in tracking user interactions. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the dr-logger-client package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access to sensitive data, lead to data breaches, or facilitate other malicious activities. The issue affects all versions starting from 0, 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 dr-logger-client

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 removing the dr-logger-client package from your project until a secure version is released. You can do this by running the command: 'npm uninstall dr-logger-client'. Additionally, monitor your application for any suspicious activities during this period.

Conclusion

The discovery of malicious code in the dr-logger-client package poses a serious threat to applications utilizing it. Immediate action is required to mitigate risks by updating or removing the package. Stay informed about updates and utilize tools like Vulert to monitor your applications for vulnerabilities.

See every vulnerability recorded for dr-logger-client →

Share this vulnerability

FAQ

dr-logger-client is an npm package used for logging client-side events in web applications.

The malicious code found in dr-logger-client can potentially allow unauthorized access to sensitive data and lead to security breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application by uploading your package-lock.json file at Vulert Scanner.

As of now, a patched version has not been released. Users are advised to monitor the package repository for updates.

If you cannot update the package right away, consider removing it from your project and monitoring for any suspicious activities.

How To Fix

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

npm uninstall dr-logger-client

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