Malicious Code Detected in cli-janus-norma-lightyear Package

cli-janus-norma-lightyear Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17109: Malicious code in cli-janus-norma-lightyear (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 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

The cli-janus-norma-lightyear package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and various features. However, this package has been found to contain malicious code that poses a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the cli-janus-norma-lightyear package stems from the inclusion of malicious code that can compromise the integrity of applications using this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in 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 cli-janus-norma-lightyear

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 cli-janus-norma-lightyear package until a secure version is released. It is advisable to look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the cli-janus-norma-lightyear package highlights the importance of vigilance in using open-source libraries. Users are urged to take immediate action to protect their applications and data by removing the affected package and seeking alternatives.

See every vulnerability recorded for cli-janus-norma-lightyear →

Share this vulnerability

FAQ

cli-janus-norma-lightyear is an npm package used in JavaScript applications for specific functionalities.

The package was found to contain malicious code that can compromise application security and user data.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Immediately remove the cli-janus-norma-lightyear package from your project and look for alternative solutions.

Currently, there is no patch available. Users should monitor the package repository for updates.

How To Fix

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

npm uninstall cli-janus-norma-lightyear

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