Malicious Code Detected in @wptv/logger: Security Risk Alert

@wptv/logger Updated 02 Oct 2025

Summary

23/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6267: Malicious code in @wptv/logger (npm). Affects @wptv/logger versions >= 1.0.0. 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 @wptv/logger package is a logging utility designed for use in JavaScript applications, particularly within the Node.js ecosystem. It provides developers with a straightforward way to log messages, errors, and other information during application runtime. However, this package has been identified as having a critical vulnerability that allows it to communicate with a domain associated with malicious activity, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the @wptv/logger package originates from its ability to connect to a potentially harmful domain. This could lead to data exfiltration, unauthorized access, or other malicious actions that compromise the integrity and security of the application. The issue was introduced in version 1.0.0, and it is crucial for developers to be aware of the risks associated with using this package in its current state.

How To Fix

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

npm uninstall @wptv/logger

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

If an immediate update is not feasible, consider removing the @wptv/logger package from your project and replacing it with an alternative logging library that does not have known vulnerabilities. This can be done by uninstalling the package with the command: npm uninstall @wptv/logger.

Conclusion

The @wptv/logger package has been identified as having a serious vulnerability that can lead to malicious activity. It is essential for developers to take immediate action to update or replace the package to ensure the security of their applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for @wptv/logger →

Share this vulnerability

FAQ

The vulnerability allows the package to communicate with a domain linked to malicious activities, which can compromise application security.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Consider removing the @wptv/logger package and replacing it with a secure alternative until a patched version is available.

Yes, continuing to use the vulnerable package may expose your application to data breaches and unauthorized access.

How To Fix

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

npm uninstall @wptv/logger

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