Critical Malicious Code Vulnerability in @ownbackup/ob-loader Package

@ownbackup/ob-loader Updated 23 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192705: Malicious code in @ownbackup/ob-loader (npm). Affects @ownbackup/ob-loader versions 25.0.0. 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 @ownbackup/ob-loader package is a Node.js library used for loading and managing backup data efficiently. It is designed to streamline the backup process for applications, ensuring data integrity and availability. However, this package has been identified with a serious vulnerability that exposes users to potential malicious code execution.

Vulnerability Detail

This vulnerability stems from the inclusion of malicious code in version 25.0.0 of the @ownbackup/ob-loader package. The malicious code can compromise the security of applications utilizing this package, leading to unauthorized access, data breaches, or further exploitation of the system. The origin of this issue is linked to a malicious actor who has manipulated the package to introduce harmful functionalities.

How To Fix

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

npm uninstall @ownbackup/ob-loader

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 affected version (25.0.0) of the @ownbackup/ob-loader package until a patch is applied. It is advisable to revert to a previous stable version that does not contain the vulnerability.

Conclusion

The @ownbackup/ob-loader package has been identified with a critical vulnerability due to the presence of malicious code. It is essential for users to take immediate action by updating the package to a secure version or implementing workarounds to mitigate risks. Regular monitoring and updates are crucial for maintaining application security.

See every vulnerability recorded for @ownbackup/ob-loader →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access to sensitive data and potential exploitation of the system.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

If an immediate update is not possible, consider reverting to a previous stable version of the package until a patch is available.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.

You can find more details about the package on its official repository or npm page.

How To Fix

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

npm uninstall @ownbackup/ob-loader

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