Critical Malicious Code Injection in log-sink-testmetest Package
Summary
MAL-2026-18179: Malicious code in log-sink-testmetest (npm). Affects log-sink-testmetest versions 1.0.1. 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 log-sink-testmetest package, available on npm, is designed for logging and data handling within JavaScript applications. However, version 1.0.1 of this package has been found to contain malicious code that executes during installation, posing a significant security risk to users. This vulnerability allows attackers to potentially steal sensitive data from affected systems.
Vulnerability Detail
The vulnerability stems from the presence of a binding.gyp file in the log-sink-testmetest package, which uses GYP command expansion to execute an obfuscated JavaScript file (index.js) during the npm install process. This file decrypts an encrypted payload (data.bin) and executes it, which can lead to unauthorized access to sensitive information. The malicious code is designed to evade detection by using multiple layers of obfuscation and can execute in an alternate runtime environment (Bun), making it particularly dangerous.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall log-sink-testmetestIf 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 avoid using the log-sink-testmetest package until a patched version is released. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The log-sink-testmetest package has a critical vulnerability that allows for malicious code execution during installation. Users are advised to update to a patched version or remove the package until a fix is available. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for log-sink-testmetest →
FAQ
log-sink-testmetest is an npm package used for logging and data handling in JavaScript applications.
The vulnerability executes malicious code during the installation of the package, which can lead to data theft.
You should immediately update the package to a patched version or remove it from your project.
Yes, Vulert can monitor your project for open-source vulnerabilities in real-time using just your package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
