Malicious Code Injection in mobioffice-cli: A Critical Security Threat

mobioffice-cli Updated 02 Oct 2025

Summary

16/09/2025
CRITICAL
No i
Critical
Not published

MAL-2025-47404: Malicious code in mobioffice-cli (npm). Affects mobioffice-cli versions 1.0.3. 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

mobioffice-cli is an npm package designed for managing and automating tasks related to office documents. It provides users with tools to streamline their workflow and enhance productivity. However, this package has been compromised, leading to the introduction of malicious code that poses significant security risks to users and their projects.

Vulnerability Detail

The vulnerability stems from the mobioffice-cli package being compromised by the Shai-Hulud NPM worm. This malicious payload is designed to steal tokens and credentials from users, subsequently publishing this sensitive information to GitHub. Furthermore, it propagates itself to other NPM packages owned by the affected user, amplifying the potential damage. The presence of embedded malicious code (CWE-506) makes this vulnerability particularly concerning, as it can lead to unauthorized access and data breaches.

How To Fix

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

npm uninstall mobioffice-cli

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, users can remove the mobioffice-cli package from their projects until a secure version is confirmed. This can be achieved by executing the command: 'npm uninstall mobioffice-cli'. Additionally, users should review their NPM packages for any unauthorized changes and monitor their accounts for suspicious activity.

Conclusion

The mobioffice-cli package has been compromised, introducing a severe security vulnerability that can lead to the theft of sensitive information. Users are urged to update or uninstall the package immediately and monitor their projects for any signs of unauthorized access. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.

See every vulnerability recorded for mobioffice-cli →

Share this vulnerability

FAQ

The malicious code is designed to steal sensitive tokens and credentials from users and publish them to GitHub, potentially compromising user accounts.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file with Vulert's playground, you can determine if your application is affected.

If you have installed mobioffice-cli, it is crucial to uninstall the package immediately and check for any unauthorized changes in your project.

To prevent future vulnerabilities, regularly update your packages, use tools like Vulert to monitor for vulnerabilities, and audit your dependencies frequently.

Failing to address this vulnerability can lead to unauthorized access to your accounts, data breaches, and the propagation of malicious code to other projects.

How To Fix

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

npm uninstall mobioffice-cli

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