Malicious Code Detected in decoherence-pulsar-eclipse-forever Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18164: Malicious code in decoherence-pulsar-eclipse-forever (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The decoherence-pulsar-eclipse-forever package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for its unique features that enhance application performance and user experience. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the decoherence-pulsar-eclipse-forever package arises from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue originates from version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall decoherence-pulsar-eclipse-forever

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 remove the decoherence-pulsar-eclipse-forever package from their project until a secure version is released. This can be done using the command: 'npm uninstall decoherence-pulsar-eclipse-forever'.

Conclusion

The decoherence-pulsar-eclipse-forever package has been found to contain malicious code, posing serious security risks to applications that utilize it. Users are advised to update or remove the package to mitigate these risks. Monitoring tools like Vulert can assist in identifying such vulnerabilities in the future.

See every vulnerability recorded for decoherence-pulsar-eclipse-forever →

Share this vulnerability

FAQ

It is an npm package used in JavaScript applications for enhancing performance and user experience.

The malicious code was identified through security audits and reports from tools like Amazon Inspector.

The risks include unauthorized access, data breaches, and potential harm to the integrity of applications using the package.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall decoherence-pulsar-eclipse-forever

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