Malicious Code Detected in windowston Package: Version 3.19.2

windowston Updated 28 Feb 2026

Summary

26/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1057: Malicious code in windowston (npm). Affects windowston versions 3.19.2. 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 'windowston' package is a logging library for Node.js applications, designed to provide a simple and flexible way to log messages. It supports various transports for logging, including console and file outputs. However, version 3.19.2 has been flagged for malicious behavior, which compromises the security of applications using this package.

Vulnerability Detail

The vulnerability in the 'windowston' package arises from its ability to communicate with a domain linked to malicious activities. This behavior indicates that the package may execute commands that can lead to unauthorized access or control over the affected system. The malicious nature of this package poses significant risks, including data breaches, system compromise, and potential exploitation of other connected systems.

How To Fix

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

npm uninstall windowston

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 immediate updating is not feasible, consider removing the 'windowston' package from your project and replacing it with an alternative logging library that has a proven track record of security. For example, you can use 'winston' as a replacement: npm install winston.

Conclusion

The 'windowston' package version 3.19.2 has been identified as malicious, posing significant risks to applications that utilize it. It is crucial to update to a secure version or switch to an alternative logging library to mitigate potential threats. Regular monitoring of dependencies using tools like Vulert can help maintain application security.

See every vulnerability recorded for windowston →

Share this vulnerability

FAQ

The 'windowston' package is a logging library for Node.js applications that provides various logging functionalities.

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 if your application is affected.

If you cannot update the package right away, consider removing it and using a secure alternative logging library, such as 'winston'.

Detailed information about the vulnerability can be found on the OpenSSF Package Analysis project page and the GitHub repository for malicious packages.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

How To Fix

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

npm uninstall windowston

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