Malicious Code Detected in shop-state Package: Version 999.1.0 Vulnerability

shop-state Updated 05 Jan 2026

Summary

05/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-48: Malicious code in shop-state (npm). Affects shop-state versions 999.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 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 'shop-state' package is a JavaScript library used in npm ecosystems for managing application state in a structured manner. It provides developers with tools to efficiently handle state changes and data flow within their applications. However, the package version 999.1.0 has been flagged for malicious activity, raising concerns about its security and integrity.

Vulnerability Detail

The vulnerability in the 'shop-state' package arises from its communication with a domain known for malicious activities. This behavior poses significant risks, including potential data breaches, unauthorized access to sensitive information, and exploitation of the affected systems. The origin of this vulnerability has been traced back to the package's design, which allows it to connect to external domains without adequate security checks.

How To Fix

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

npm uninstall shop-state

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 'shop-state' package from your project until a secure version is available. You can do this by running: npm uninstall shop-state. Additionally, monitor your application for any unusual behavior that may indicate exploitation of this vulnerability.

Conclusion

The 'shop-state' package version 999.1.0 has been identified as malicious due to its communication with harmful domains. It is crucial for developers to update or remove this package to safeguard their applications from potential threats. Utilizing tools like Vulert can help in monitoring vulnerabilities effectively.

See every vulnerability recorded for shop-state →

Share this vulnerability

FAQ

The 'shop-state' package is used for managing application state in JavaScript applications, providing tools for efficient state management.

Version 999.1.0 is considered malicious because it communicates with a domain associated with malicious activities, posing security risks.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you cannot update the package immediately, consider uninstalling it and monitoring your application for any unusual behavior.

For more information about open-source vulnerabilities, you can visit Vulert at https://vulert.com, which helps monitor and alert for vulnerabilities in real-time.

How To Fix

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

npm uninstall shop-state

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