Critical Malicious Code Vulnerability in @schedaero/shared Package

@schedaero/shared Updated 04 Mar 2026

Summary

25/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1231: Malicious code in @schedaero/shared (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 @schedaero/shared package is a component of the npm ecosystem, primarily used for sharing functionalities within applications related to the Schedaero platform. It is designed to facilitate seamless integration and enhance user experience by providing essential features. However, this package has been identified as malicious, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @schedaero/shared package. This code is designed to execute preinstall scripts, exfiltrate sensitive data, and force process exits, all while impersonating the legitimate schedaero.com domain. The malicious nature of this package can lead to severe consequences, including unauthorized access to user data and potential system compromise.

How To Fix

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

npm uninstall @schedaero/shared

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, you can avoid using the @schedaero/shared package altogether and look for alternative packages that provide similar functionalities without the associated risks.

Conclusion

The @schedaero/shared package has been identified as malicious, posing serious risks to users and their applications. It is essential to take immediate action by uninstalling the package and monitoring for updates or alternatives. Utilizing tools like Vulert can help in maintaining the security of your open-source dependencies.

See every vulnerability recorded for @schedaero/shared →

Share this vulnerability

FAQ

The malicious code is designed to execute unauthorized scripts, exfiltrate data, and impersonate legitimate services.

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

You should immediately uninstall the package using 'npm uninstall @schedaero/shared' and look for alternatives.

Yes, the malicious code can lead to data exfiltration and unauthorized access, making it a significant security risk.

Regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

How To Fix

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

npm uninstall @schedaero/shared

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