Malicious Code Detected in so-demo Package - Security Risk Alert

so-demo Updated 02 Oct 2025

Summary

12/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6126: Malicious code in so-demo (npm). Affects so-demo versions >= 55.3.1. 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 'so-demo' package is an npm library designed for demonstration purposes, often used in testing and educational environments. It provides various functionalities that simulate real-world applications. However, this package has been identified to communicate with a domain associated with malicious activity, raising significant security concerns for users and developers relying on it.

Vulnerability Detail

The vulnerability in the 'so-demo' package stems from its communication with a domain linked to malicious activities. This could potentially lead to data breaches, unauthorized access, or the execution of harmful code within applications that utilize this package. The issue was introduced in version 55.3.1, making it crucial for users to be aware of the risks associated with this version.

How To Fix

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

npm uninstall so-demo

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 temporary measure, users can avoid using the 'so-demo' package until a secure version is released. Alternatively, consider using a different package that offers similar functionality without the associated risks.

Conclusion

The 'so-demo' package has been flagged for a serious vulnerability due to its communication with a malicious domain. Users are strongly advised to update their packages and consider alternative solutions until a secure version is confirmed. Regular monitoring with tools like Vulert can help maintain application security.

See every vulnerability recorded for so-demo →

Share this vulnerability

FAQ

The vulnerability involves the package communicating with a domain known for malicious activities, posing a security risk.

You can use Vulert, which monitors and alerts for open-source vulnerabilities. Visit Vulert Scanner to check your application without signing up.

You should update the package to the latest patched version by running 'npm update so-demo' in your terminal.

While specific exploits have not been detailed, the potential for data breaches and unauthorized access exists due to the malicious domain communication.

Failing to address this vulnerability could lead to severe security breaches, including data loss, unauthorized access, and compromised application integrity.

How To Fix

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

npm uninstall so-demo

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