Critical Malicious Code Vulnerability in sync365 Package

sync365 Updated 02 Oct 2025

Summary

08/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5731: Malicious code in sync365 (npm). Affects sync365 versions 2.14.51. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The sync365 package is a Node.js library designed for synchronizing data across various platforms. It is commonly used in web applications to facilitate seamless data integration. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and organizations relying on it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the sync365 package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems. The malicious nature of the code has been confirmed by security researchers, and it is classified under the CWE-506 category, which pertains to embedded malicious code.

How To Fix

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

npm uninstall sync365

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

Currently, the best workaround is to uninstall the sync365 package. You can do this by running the following command in your terminal: npm uninstall sync365. Ensure that you also check for any other dependencies that may be affected by this removal.

Conclusion

The sync365 package contains malicious code that poses a serious security threat to any system it is installed on. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor and manage vulnerabilities in your software effectively.

See every vulnerability recorded for sync365 →

Share this vulnerability

FAQ

Immediately uninstall the sync365 package and rotate any sensitive information stored on the affected system.

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.

As of now, there is no patched version available. The recommendation is to remove the package entirely.

Keeping sync365 installed poses a significant risk of data breaches and unauthorized access to sensitive information.

It is advisable to review the security of other packages from the same author, as they may also be vulnerable.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall sync365

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