Malicious Code Detected in @zinley/orion Package: Version 1.2.31 and Above

@zinley/orion Updated 28 Feb 2026

Summary

27/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1060: Malicious code in @zinley/orion (npm). Affects @zinley/orion versions 1.2.31 – 1.2.39. 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 @zinley/orion package is an npm library designed for various functionalities within JavaScript applications. It is utilized by developers for its ease of integration and feature set. However, a recent analysis has flagged this package as malicious due to the execution of harmful commands, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability originates from the malicious behavior embedded within the @zinley/orion package, specifically in version 1.2.31 and subsequent versions. The package executes commands that can compromise the security of the host system, potentially leading to unauthorized access, data breaches, or system corruption. This vulnerability is particularly concerning as it affects a widely used npm package, making many applications susceptible to exploitation.

How To Fix

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

npm uninstall @zinley/orion

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, if immediate updating is not feasible, consider removing the @zinley/orion package from your project until a secure version is confirmed. This can be done using the command: npm uninstall @zinley/orion.

Conclusion

The @zinley/orion package has been identified as malicious, with significant risks associated with its use in applications. It is imperative for developers to update to the latest version or remove the package to safeguard their projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for @zinley/orion →

Share this vulnerability

FAQ

The package executes commands that can lead to unauthorized access and potential data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Versions 1.2.31 and above of the @zinley/orion package are flagged as malicious.

Yes, updating to the latest version of @zinley/orion will resolve the vulnerability.

Consider removing the package from your project until a secure version is confirmed.

How To Fix

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

npm uninstall @zinley/orion

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