Malicious Code Detected in @ownbackup/icons Package - Security Alert

@ownbackup/icons Updated 23 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192703: Malicious code in @ownbackup/icons (npm). Affects @ownbackup/icons 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 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 @ownbackup/icons package is a library used in npm for providing a set of icons for applications. It is widely utilized in various projects for its ease of use and integration. However, recent findings have revealed that this package has been compromised, leading to potential security risks for users who have integrated it into their applications.

Vulnerability Detail

The vulnerability stems from malicious code embedded within version 25.0.0 of the @ownbackup/icons package. This code could lead to unauthorized access or manipulation of user data, posing significant risks to application integrity and user privacy. The malicious nature of the code suggests that it was intentionally inserted, making it imperative for users to take immediate action to mitigate potential damage.

How To Fix

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

npm uninstall @ownbackup/icons

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 remove the @ownbackup/icons package from their project until a secure version is confirmed. This can be done using the command: 'npm uninstall @ownbackup/icons'. Additionally, consider using alternative icon libraries that are known to be secure.

Conclusion

The discovery of malicious code in the @ownbackup/icons package highlights the importance of vigilance in software dependencies. Users must take proactive steps to secure their applications by updating or removing affected packages. Utilizing tools like Vulert can aid in monitoring vulnerabilities effectively.

See every vulnerability recorded for @ownbackup/icons →

Share this vulnerability

FAQ

The malicious code is designed to compromise user data and application security, potentially allowing unauthorized access.

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.

If an immediate update is not possible, consider removing the package temporarily and using alternative libraries until a secure version is available.

Detailed information can be found on the GitHub repository of the package or through security advisories related to npm packages.

Updating the package should not cause data loss, but it is always recommended to back up your project before making significant changes.

How To Fix

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

npm uninstall @ownbackup/icons

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