Malicious Code Detected in diaction Package - Security Alert

diaction Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18429: Malicious code in diaction (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 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

The diaction package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various tasks, but its recent identification as containing malicious code raises significant security concerns. Users of this package may unknowingly expose their applications to risks due to the embedded harmful code.

Vulnerability Detail

The diaction package has been found to contain malicious code that can compromise the security of applications utilizing it. This vulnerability originated from the package's codebase, which was intentionally altered to include harmful scripts. The ramifications of this vulnerability can include unauthorized access to sensitive data, data manipulation, or even complete system compromise, depending on how the malicious code is executed within the application.

How To Fix

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

npm uninstall diaction

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 diaction package from your project until a secure version is released. You can do this by running the following command: npm uninstall diaction. Additionally, monitor your application for any unusual behavior that may indicate exploitation of the vulnerability.

Conclusion

The discovery of malicious code within the diaction package poses a significant risk to users. It is crucial to take immediate action by uninstalling the package and monitoring for any signs of exploitation. Utilizing tools like Vulert can help maintain the security of your applications by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for diaction →

Share this vulnerability

FAQ

The diaction package is an npm library used in JavaScript applications for specific functionalities, but it has recently been flagged for containing malicious code.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without signup.

If you have diaction installed, it is recommended to uninstall the package immediately and monitor your application for any unusual activity.

Currently, there is no patched version available for diaction. It is advisable to remove the package until a secure version is released.

To prevent similar vulnerabilities, regularly update your dependencies, use tools like Vulert to monitor for vulnerabilities, and review package sources before installation.

How To Fix

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

npm uninstall diaction

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