Malicious Code Detected in dasnoo-action Package - Security Alert

dasnoo-action Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17977: Malicious code in dasnoo-action (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 dasnoo-action package is an npm module designed to facilitate automation tasks within development workflows. It is commonly used in CI/CD pipelines to streamline processes. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the dasnoo-action package stems from the inclusion of malicious code that can compromise the integrity of applications using it. This code may allow unauthorized access to sensitive data or enable the execution of harmful operations within the user's environment. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall dasnoo-action

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, you can avoid using the dasnoo-action package in your workflows. Instead, consider using alternative packages that provide similar functionality without the associated security risks.

Conclusion

The discovery of malicious code in the dasnoo-action package highlights the importance of vigilance in managing dependencies. Users are urged to update or remove the package to safeguard their applications from potential threats. Regular monitoring of dependencies using tools like Vulert can help maintain security in software projects.

See every vulnerability recorded for dasnoo-action →

Share this vulnerability

FAQ

dasnoo-action is an npm module used for automating tasks in development workflows, particularly in CI/CD environments.

The malicious code can potentially compromise application security by allowing unauthorized access or executing harmful operations.

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 needing to sign up.

If an update is not available, consider removing the package from your project and using alternative solutions until a secure version is released.

Utilize tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.

How To Fix

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

npm uninstall dasnoo-action

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