Malicious Code Detected in @teamstelemetry/shared-logger: Security Alert
Summary
MAL-2025-6266: Malicious code in @teamstelemetry/shared-logger (npm). Affects @teamstelemetry/shared-logger versions >= 9.2.0. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The @teamstelemetry/shared-logger package is a logging utility designed for telemetry data collection in applications. It provides developers with a streamlined way to log events and errors, enhancing the observability of their applications. However, this package has been identified to communicate with a domain associated with malicious activity, posing a significant security risk to users.
Vulnerability Detail
The vulnerability arises from the package's communication with a malicious domain, which could lead to data exfiltration or unauthorized access to sensitive information. This issue was introduced in version 9.2.0 and can have severe ramifications, including compromised application integrity and user data breaches. The malicious activity associated with this package could potentially affect any application that utilizes it, making it crucial for developers to address this vulnerability promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @teamstelemetry/shared-loggerIf 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, you can remove the @teamstelemetry/shared-logger package from your project until a secure version is available. You can do this by executing: npm uninstall @teamstelemetry/shared-logger.
Conclusion
The @teamstelemetry/shared-logger package has been identified with a serious vulnerability due to its communication with a malicious domain. Developers are urged to update the package to the latest version or remove it until a secure version is available. Utilizing tools like Vulert can help monitor and manage such vulnerabilities effectively.
See every vulnerability recorded for @teamstelemetry/shared-logger →
FAQ
The vulnerability involves the package communicating with a domain linked to malicious activities, which can compromise application security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Consider removing the package as a temporary measure until a secure version is released. Use the command: npm uninstall @teamstelemetry/shared-logger.
It is advisable to upgrade to the latest version of @teamstelemetry/shared-logger to ensure you have the most recent security patches.
Failing to address this vulnerability could lead to data breaches, unauthorized access to sensitive information, and overall compromise of application integrity.
