Critical Malicious Code Vulnerability in workingstealer Package

workingstealer Updated 19 Nov 2025

Summary

18/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190566: Malicious code in workingstealer (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 workingstealer package is an npm module that is designed for specific functionalities within JavaScript applications. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to developers and organizations using this package, as it can lead to unauthorized access to sensitive information.

Vulnerability Detail

The vulnerability originates from the embedded malicious code within the workingstealer package. This code can fully compromise any computer that has the package installed, allowing attackers to gain control and access to all secrets and keys stored on the system. The implications of this vulnerability are severe, as it can lead to data breaches and unauthorized actions performed on behalf of the user. It is classified under CWE-506, indicating that the product contains code that appears to be malicious in nature.

How To Fix

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

npm uninstall workingstealer

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

There are no effective workarounds for this vulnerability other than removing the package and securing your system. It is recommended to monitor your environment for any signs of unauthorized access after the removal.

Conclusion

The workingstealer package poses a critical security risk due to the embedded malicious code that can compromise any system it is installed on. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for workingstealer →

Share this vulnerability

FAQ

Immediately uninstall the workingstealer package using the command npm uninstall workingstealer and rotate all secrets and keys stored on the affected system.

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

Keeping the workingstealer package installed can lead to unauthorized access to sensitive information, data breaches, and potential control over your system by malicious actors.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and ensure that you only use trusted packages from reputable sources.

This vulnerability is classified under CWE-506, which indicates that the product contains code that appears to be malicious in nature.

How To Fix

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

npm uninstall workingstealer

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