Malicious Code in symphony-list (npm)

symphony-list Updated 02 Oct 2025

Summary

05/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8430: Malicious code in symphony-list (npm). Affects symphony-list versions 1.0.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 package 'symphony-list' is an npm package that provides functionality related to symphony lists. It is commonly used in JavaScript projects that require list manipulation and management. The package is vulnerable to a specific issue related to malicious code.

Vulnerability Detail

The 'symphony-list' package has been identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity and executes commands that are linked to malicious behavior. This vulnerability poses a risk to projects that depend on 'symphony-list' as it can potentially lead to unauthorized access, data breaches, or other malicious activities.

How To Fix

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

npm uninstall symphony-list

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 specific workaround provided for this vulnerability. The best course of action is to remove the 'symphony-list' package and find a secure replacement.

Conclusion

The 'symphony-list' package has been identified as malicious and poses a risk to projects that use it. To ensure the security of your project, it is recommended to remove the package and find a trusted alternative. Regularly updating and reviewing dependencies is also crucial to mitigate the risk of known vulnerabilities. For further support or assistance, you can contact DevNack.com.

See every vulnerability recorded for symphony-list →

Share this vulnerability

FAQ

This vulnerability can lead to unauthorized access, data breaches, or other malicious activities in projects that use the 'symphony-list' package.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and the tool will alert you if any open-source vulnerabilities, including this one, are found.

There are no known fixes or patches available for the 'symphony-list' package. It is recommended to remove the package and find a secure alternative.

The best way to mitigate the risk is to remove the 'symphony-list' package and replace it with a trusted alternative. There are no known methods to mitigate the risk while keeping the package in your project.

For further support or assistance regarding vulnerability remediation, you can contact info@devnack.com. They can provide guidance and help you address any concerns related to this vulnerability.

How To Fix

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

npm uninstall symphony-list

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