Malicious Code Detected in privmx-crypto Package - Security Alert

privmx-crypto Updated 02 Oct 2025

Summary

18/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6118: Malicious code in privmx-crypto (npm). Affects privmx-crypto versions >= 1338.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 privmx-crypto package is an npm library designed for cryptographic operations within applications. It provides essential functionalities for secure data handling and encryption. However, it has been identified as communicating with a domain linked to malicious activities, posing a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability in the privmx-crypto package arises from its communication with a domain associated with malicious activity. This can lead to unauthorized data access, potential data breaches, and exploitation of the application using this package. The issue was introduced in version 1338.0.0, making it crucial for users to be aware of the risks involved with this version.

How To Fix

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

npm uninstall privmx-crypto

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 measure, you can remove the privmx-crypto package from your project if it is not essential. This can be done using the command: npm uninstall privmx-crypto. Alternatively, consider using a different package that provides similar cryptographic functionalities without the associated risks.

Conclusion

The privmx-crypto package has been flagged for a serious vulnerability due to its connection with a malicious domain. Users are strongly advised to update or remove the package to safeguard their applications. Regular monitoring using tools like Vulert can help maintain security against such vulnerabilities.

See every vulnerability recorded for privmx-crypto →

Share this vulnerability

FAQ

The privmx-crypto package is an npm library used for cryptographic operations, including data encryption and secure data handling.

The vulnerability involves the package communicating with a domain linked to malicious activities, which can compromise application security.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

If immediate updates are not possible, consider removing the package or using an alternative library until a secure version is available.

The vulnerability was identified by Amazon Inspector, a security tool that helps detect vulnerabilities in software packages.

How To Fix

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

npm uninstall privmx-crypto

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