Malicious code in ory-demo (npm)

ory-demo Updated 02 Oct 2025

Summary

21/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8550: Malicious code in ory-demo (npm). Affects ory-demo versions 22.2.2 – 22.2.6. 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

ory-demo is an npm package that is used for [provide brief description of the package's functionality and key attributes]. It is widely used in [mention relevant industries or applications]. However, the package has been identified as containing malicious code that communicates with a domain associated with malicious activity.

Vulnerability Detail

The malicious code found in ory-demo poses a significant security risk. It can potentially compromise the security and integrity of systems that use this package. The code communicates with a domain that is known for malicious activity, which can lead to unauthorized access, data breaches, and other malicious actions. It is crucial to address this vulnerability promptly to prevent any potential harm.

How To Fix

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

npm uninstall ory-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

There is no known workaround for this vulnerability. It is crucial to update the package to a non-malicious version as soon as possible.

Conclusion

The presence of malicious code in ory-demo poses a significant security risk. It is crucial to update the package to a non-malicious version and regularly monitor for updates and security advisories. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for ory-demo →

Share this vulnerability

FAQ

ory-demo is an npm package that [provide a brief description of the package's functionality and purpose].

The malicious code in ory-demo can potentially compromise the security and integrity of systems that use this package. It communicates with a domain associated with malicious activity, which can lead to unauthorized access, data breaches, and other malicious actions.

To fix this vulnerability, it is recommended to update ory-demo to a non-malicious version. Regularly monitoring for updates and security advisories related to ory-demo is also essential.

There is no known workaround for this vulnerability. It is crucial to update the package to a non-malicious version as soon as possible.

For more information about ory-demo and this vulnerability, you can refer to the package's source code and the provided link to the vulnerability details in the OpenSSF Package Analysis project.

How To Fix

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

npm uninstall ory-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