Malicious Code Detected in Datomico Package - Security Alert

datomico Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18068: Malicious code in datomico (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

Datomico is an npm package designed for data manipulation and interaction with various databases. It offers functionalities that allow developers to easily manage and query data. However, recent findings have revealed that the package contains malicious code, posing a significant security risk to users who integrate it into their applications.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the datomico package, which was introduced in version 0. This code can potentially compromise user data, lead to unauthorized access, or facilitate other malicious activities. The implications of this vulnerability are severe, as it can affect any application that relies on this package, making it crucial for developers to take immediate action.

How To Fix

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

npm uninstall datomico

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

Conclusion

The discovery of malicious code in the datomico package poses a serious security risk to developers and users. Immediate action is required to mitigate potential threats by updating or removing the package. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for datomico →

Share this vulnerability

FAQ

The malicious code can compromise user data and lead to unauthorized access, posing a significant security threat.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If an immediate update is not possible, consider removing the package from your project as a temporary measure until a secure version is released.

While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation, making it critical to address the issue promptly.

You can find more information about the datomico package on its official npm page or GitHub repository.

How To Fix

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

npm uninstall datomico

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