Malicious Code Detected in angular-bookly Package - Security Alert

angular-bookly Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14523: Malicious code in angular-bookly (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 angular-bookly package is a library designed for creating interactive and engaging online books using Angular. It provides features such as customizable layouts, multimedia integration, and user-friendly navigation. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the angular-bookly package. This code can potentially compromise the integrity of applications using this library, leading to unauthorized access, data breaches, or other malicious activities. The issue affects all versions of the package starting from its introduction, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall angular-bookly

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, consider using alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your application has robust security measures in place to mitigate potential threats from malicious code.

Conclusion

The discovery of malicious code in the angular-bookly package highlights the importance of maintaining secure dependencies in software development. Users are urged to take immediate action to protect their applications from potential threats.

See every vulnerability recorded for angular-bookly →

Share this vulnerability

FAQ

angular-bookly is a library for creating interactive online books using Angular, offering features like customizable layouts and multimedia integration.

The specific nature of the malicious code has not been disclosed, but it poses significant security risks, including unauthorized access and data breaches.

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

Immediately remove the angular-bookly package from your project and look for alternative packages or wait for a patched version to be released.

Regularly check package repositories and use tools like Vulert to monitor your dependencies for any vulnerabilities.

How To Fix

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

npm uninstall angular-bookly

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