Malicious Code Detected in spire.officejs-document Package - Version 1.0.0

spire.officejs-document Updated 05 Jan 2026

Summary

05/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-41: Malicious code in spire.officejs-document (npm). Affects spire.officejs-document versions 1.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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The spire.officejs-document package is an npm library designed for handling office document functionalities within JavaScript applications. It provides features for document manipulation and integration with various office formats. However, this package has been flagged for malicious behavior, specifically for communicating with a domain linked to malicious activities, raising serious security concerns for users and developers relying on it.

Vulnerability Detail

The vulnerability in the spire.officejs-document package arises from its version 1.0.0, which has been identified as malicious by the OpenSSF Package Analysis project. The package's communication with a domain associated with malicious activities poses significant risks, including potential data breaches, unauthorized access, and exploitation of user systems. This vulnerability highlights the importance of scrutinizing third-party packages for security threats.

How To Fix

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

npm uninstall spire.officejs-document

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 workaround, consider using alternative packages that offer similar document handling capabilities without the associated risks. You can search for trusted npm packages that have been vetted for security and reliability.

Conclusion

The spire.officejs-document package version 1.0.0 has been identified as malicious due to its communication with a harmful domain. Users are advised to remove this package from their projects and seek safer alternatives. Continuous monitoring of dependencies is crucial for maintaining application security.

See every vulnerability recorded for spire.officejs-document →

Share this vulnerability

FAQ

The spire.officejs-document package is an npm library for manipulating office documents in JavaScript applications.

It is considered malicious because it communicates with a domain linked to malicious activities, posing security risks.

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.

It is recommended to uninstall the package immediately and look for alternative solutions that do not pose security risks.

Regularly audit your dependencies, use tools like Vulert for monitoring vulnerabilities, and only use packages from trusted sources.

How To Fix

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

npm uninstall spire.officejs-document

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