Malicious Code Detected in archaeometry-umbriel-callback-io Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14788: Malicious code in archaeometry-umbriel-callback-io (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 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 archaeometry-umbriel-callback-io package is an npm library designed for handling callback functions in archaeological data processing. It is utilized by developers to streamline workflows and enhance data management. However, this package has been found to contain malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the archaeometry-umbriel-callback-io package. This code can lead to unauthorized access, data breaches, or other harmful actions within the application. The malicious nature of this code can compromise the integrity and security of systems utilizing this package, making it critical for developers to address this issue promptly.

How To Fix

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

npm uninstall archaeometry-umbriel-callback-io

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 archaeometry-umbriel-callback-io package from your project until a secure version is released. You can do this by executing the command: npm uninstall archaeometry-umbriel-callback-io.

Conclusion

The discovery of malicious code in the archaeometry-umbriel-callback-io package highlights the importance of vigilance in managing open-source dependencies. Developers are urged to update or remove the affected package to safeguard their applications.

See every vulnerability recorded for archaeometry-umbriel-callback-io →

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions, potentially compromising user data and application security.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks.

While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation.

Regularly check for updates and use tools like Vulert to monitor your dependencies for vulnerabilities.

How To Fix

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

npm uninstall archaeometry-umbriel-callback-io

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