Malicious Code Detected in context-log Package - Security Alert

context-log Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17516: Malicious code in context-log (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 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 context-log package is an npm library designed for logging context-specific information in applications. It provides developers with tools to manage and output logs effectively, enhancing debugging and monitoring capabilities. However, a recent discovery has revealed that this package contains malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the context-log package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected applications. The malicious nature of the code was identified by security researchers, emphasizing the importance of vigilance when using third-party packages.

How To Fix

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

npm uninstall context-log

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, you can remove the context-log package from your project until a secure version is released. You can do this by executing the command: npm uninstall context-log. Consider using alternative logging libraries that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the context-log package poses a serious threat to applications that utilize it. It is essential for developers to update their dependencies promptly and consider using tools like Vulert to monitor for vulnerabilities in real-time. By staying informed and proactive, developers can safeguard their applications against potential attacks.

See every vulnerability recorded for context-log →

Share this vulnerability

FAQ

The context-log package is an npm library used for logging context-specific information in applications, aiding in debugging and monitoring.

The malicious code found in the context-log package can lead to unauthorized access and potential data breaches in applications that use it.

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

If you cannot update the package right away, consider uninstalling it and using an alternative logging library until a secure version is available.

The vulnerability was identified by security researchers from Amazon Inspector, who reported the presence of malicious code in the context-log package.

How To Fix

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

npm uninstall context-log

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