Malicious Code Detected in authorly Package - Security Alert

authorly Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15101: Malicious code in authorly (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The authorly package is a Node.js library designed for managing and enhancing author-related functionalities in applications. It provides features such as author profile management, book listings, and integration with various publishing platforms. However, the package has been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the authorly package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code can potentially lead to unauthorized access, data breaches, or other malicious activities. The issue affects all versions starting from 0, making it critical for users to take immediate action to protect their applications.

How To Fix

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

npm uninstall authorly

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 removing the authorly package from your project until a secure version is released. You can do this by executing: npm uninstall authorly. This will help mitigate the risk of exposure to the malicious code.

Conclusion

The discovery of malicious code in the authorly package poses a serious threat to applications utilizing it. Immediate action is required to update or remove the package to safeguard against potential security breaches. Regular monitoring of dependencies is crucial to maintain application security.

See every vulnerability recorded for authorly →

Share this vulnerability

FAQ

The authorly package is a Node.js library used for managing author-related functionalities in applications.

The malicious code can lead to unauthorized access and potential data breaches in applications that use the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

As a temporary measure, consider uninstalling the authorly package to mitigate risks until a secure version is available.

Utilize tools like Vulert to monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

How To Fix

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

npm uninstall authorly

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