Malicious Code Detected in emerald-opal-pjs139-project: A Critical Security Alert

emerald-opal-pjs139-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19611: Malicious code in emerald-opal-pjs139-project (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 package 'emerald-opal-pjs139-project' is an npm package designed for specific project functionalities within the Node.js ecosystem. It is utilized by developers to streamline certain tasks in their applications. However, this package has been identified as containing malicious code, posing significant security risks to any application that integrates it.

Vulnerability Detail

The vulnerability in 'emerald-opal-pjs139-project' stems from the inclusion of malicious code within the package. This code can potentially compromise the security of applications that utilize the package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced from version 0 and affects all subsequent versions, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall emerald-opal-pjs139-project

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 'emerald-opal-pjs139-project' package altogether until a secure version is released. It is advisable to review the project's dependencies and consider alternative packages that offer similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the 'emerald-opal-pjs139-project' npm package poses a serious threat to application security. Users must take immediate action to remove the package and monitor their applications for any potential impacts. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.

See every vulnerability recorded for emerald-opal-pjs139-project →

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions within the application, potentially leading to data theft or system compromise.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

Immediately remove the package from your project and replace it with a secure alternative. Monitor your application for any unusual activity.

Currently, there is no patched version available. Users are advised to remove the package until a secure version is released.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories for the packages you use.

How To Fix

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

npm uninstall emerald-opal-pjs139-project

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