Malicious Code Detected in easy-visualize-decode-phi-meta Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19089: Malicious code in easy-visualize-decode-phi-meta (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 easy-visualize-decode-phi-meta package is an npm library designed for visualizing and decoding data related to phi meta-analysis. It offers functionalities that assist researchers and developers in interpreting complex datasets. However, this package has been found to contain malicious code, posing significant risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the easy-visualize-decode-phi-meta package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the user's environment. The malicious nature of this vulnerability was identified by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security risks.

How To Fix

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

npm uninstall easy-visualize-decode-phi-meta

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 workaround, users can replace the easy-visualize-decode-phi-meta package with alternative libraries that provide similar functionalities without the associated risks. It is advisable to conduct thorough research on the alternatives to ensure they are secure and well-maintained.

Conclusion

The easy-visualize-decode-phi-meta package has been identified as containing malicious code, which poses a significant risk to users. It is crucial to remove this package and consider alternatives while keeping an eye on updates and patches. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.

See every vulnerability recorded for easy-visualize-decode-phi-meta →

Share this vulnerability

FAQ

It is an npm library used for visualizing and decoding phi meta-analysis data.

The malicious code can lead to unauthorized access and potential data breaches.

You can use Vulert's playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

Remove the package immediately and look for secure alternatives or patches.

Vulert monitors and alerts for open-source vulnerabilities in real-time using just the package-lock.json file.

How To Fix

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

npm uninstall easy-visualize-decode-phi-meta

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