Critical Malicious Code Vulnerability in wos-library Package

wos-library Updated 22 Sep 2026

Summary

21/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16373: Malicious code in wos-library (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The wos-library package is an npm library designed for various functionalities in JavaScript applications. It is widely used for its ease of integration and utility in web development. However, it has been identified to contain malicious code that compromises the security of any system where it is installed, making it a significant risk for developers and organizations relying on it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the wos-library package. This code can grant unauthorized access to an attacker, leading to potential data breaches and loss of sensitive information. The malicious nature of this code means that any system running this package is considered fully compromised, and all secrets and keys stored on that system should be rotated immediately. The origin of this vulnerability is linked to the package's malicious intent, as identified by security researchers.

How To Fix

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

npm uninstall wos-library

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 workaround, ensure that all secrets and keys stored on the compromised system are rotated from a different, secure computer. Additionally, consider using alternative libraries that provide similar functionality without the associated risks.

Conclusion

The wos-library package poses a severe security risk due to embedded malicious code. Immediate action is required to remove the package and secure any compromised systems. Developers should remain vigilant and consider using alternative libraries to mitigate risks.

See every vulnerability recorded for wos-library →

Share this vulnerability

FAQ

The wos-library is an npm package used in JavaScript applications for various functionalities, but it has been compromised with malicious code.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which monitors vulnerabilities in open-source packages.

Immediately remove the wos-library package from your project and rotate any sensitive information stored on the affected system.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

How To Fix

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

npm uninstall wos-library

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