Malicious Code Detected in js-observability Package - Security Alert

js-observability Updated 16 Jan 2026

Summary

16/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-289: Malicious code in js-observability (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The js-observability package is a JavaScript library used for monitoring and observing application performance and behavior. It is commonly utilized in Node.js environments to enhance observability in applications. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that rely on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the js-observability package, which was identified by Amazon Inspector. This malicious code can potentially compromise the integrity of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The issue affects all versions of the package starting from its introduction, making it critical for users to take immediate action.

How To Fix

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

npm uninstall js-observability

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 measure, users can remove the js-observability package from their project until a secure version is released. This can be done by executing: npm uninstall js-observability. Additionally, consider using alternative packages that provide similar functionality without the security risks.

Conclusion

The discovery of malicious code in the js-observability package highlights the importance of maintaining secure dependencies in software development. Users are urged to take immediate action by updating or removing the affected package to safeguard their applications.

See every vulnerability recorded for js-observability →

Share this vulnerability

FAQ

The js-observability package is a JavaScript library designed for monitoring and observing application performance and behavior in Node.js environments.

The malicious code was identified by Amazon Inspector during a security assessment of the package.

Using the compromised js-observability package can lead to unauthorized access, data breaches, and other malicious activities that can compromise application security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply uploading your package-lock.json file, you can check for vulnerabilities without needing to access the code.

Yes, using Vulert's playground, you can monitor your application for vulnerabilities in real-time without any signup. Visit Vulert Scanner to get started.

How To Fix

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

npm uninstall js-observability

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