Malicious code in update-packager (npm)

update-packager Updated 02 Oct 2025

Summary

15/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8518: Malicious code in update-packager (npm). Affects update-packager versions 1.0.0 – 2.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 update-packager package is an npm package used for updating packages in a project. It provides functionality to manage package updates and dependencies. However, the package has been found to contain malicious code, which poses a significant security risk to any computer that has it installed or running.

Vulnerability Detail

The malicious code in update-packager (npm) has been identified as a serious security threat. Any computer with this package installed or running should be considered fully compromised. The code allows an outside entity to gain full control of the computer, potentially leading to the theft of sensitive information and unauthorized access to systems. It is crucial to rotate all secrets and keys stored on the affected computer immediately from a different computer. Simply removing the package may not guarantee the removal of all malicious software resulting from its installation.

How To Fix

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

npm uninstall update-packager

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

There is no specific workaround mentioned for this vulnerability. It is crucial to follow the steps mentioned in the 'how_to_fix' section to mitigate the risk.

Conclusion

The presence of malicious code in the update-packager npm package poses a significant security risk. It is crucial to take immediate action by rotating all secrets and keys, removing the package, and conducting a thorough security audit. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for update-packager →

Share this vulnerability

FAQ

Update-packager is an npm package used for managing package updates and dependencies in a project.

The malicious code in update-packager can give full control of the computer to an outside entity, potentially leading to the theft of sensitive information and unauthorized access to systems.

If you have update-packager installed, it is crucial to rotate all secrets and keys stored on the affected computer from a different computer. Remove the package and conduct a thorough security audit.

Removing the update-packager package may not guarantee the removal of all malicious software resulting from its installation. A thorough security audit is recommended.

To prevent future vulnerabilities, keep all software and packages up to date and conduct regular security audits.

How To Fix

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

npm uninstall update-packager

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