Malicious Code Detected in laserlogsink Package - Version 2.1.0

laserlogsink Updated 20 Mar 2026

Summary

20/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2001: Malicious code in laserlogsink (npm). Affects laserlogsink versions 2.1.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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The 'laserlogsink' package is an npm module designed for logging laser-related data. It is utilized in various applications that require precise logging mechanisms. However, version 2.1.0 of this package has been flagged for containing malicious code that communicates with a domain linked to harmful activities, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the 'laserlogsink' package arises from its ability to communicate with a domain associated with malicious activities. This behavior can lead to data breaches, unauthorized access, and potential exploitation of the systems utilizing this package. The OpenSSF Package Analysis project identified this issue, highlighting the risks involved with using this compromised version of the package.

How To Fix

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

npm uninstall laserlogsink

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 you cannot update the package immediately, consider removing 'laserlogsink' from your project and replacing it with an alternative logging solution that does not exhibit malicious behavior.

Conclusion

The 'laserlogsink' package version 2.1.0 has been identified as malicious, posing significant security risks to applications using it. Users are encouraged to update to a secure version or consider alternative solutions to mitigate these risks. Tools like Vulert can assist in monitoring for vulnerabilities in real-time.

See every vulnerability recorded for laserlogsink →

Share this vulnerability

FAQ

The 'laserlogsink' package is an npm module used for logging laser-related data in applications.

Version 2.1.0 is flagged as malicious due to its communication with a domain linked to harmful activities, posing security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without requiring any signup.

If immediate updates are not possible, consider removing 'laserlogsink' and using an alternative logging solution until you can safely update.

Utilizing tools like Vulert can help you monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.

How To Fix

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

npm uninstall laserlogsink

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