Malicious Code Detected in acadgild Package - Security Alert

acadgild Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13971: Malicious code in acadgild (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 acadgild package is an npm library designed for educational purposes, primarily aimed at providing resources and tools for learning various programming languages and technologies. However, it has been identified as containing malicious code that poses a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability in the acadgild package stems from the inclusion of malicious code that can compromise the integrity of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall acadgild

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 may consider using alternative packages that provide similar functionality without the associated risks. Always ensure to review the security status of any package before integrating it into your project.

Conclusion

The acadgild package has been identified as containing malicious code, posing a serious security threat to users. Immediate action is required to remove the package and safeguard applications. Users are encouraged to monitor their dependencies and utilize tools like Vulert for real-time vulnerability alerts.

See every vulnerability recorded for acadgild →

Share this vulnerability

FAQ

The acadgild package is primarily used for educational purposes, providing resources and tools for learning programming languages and technologies.

The malicious code can lead to unauthorized access and potential data breaches, posing a significant security risk to applications using this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected without needing to sign up.

If immediate removal is not possible, consider using alternative packages that offer similar functionalities while ensuring they are secure.

Currently, there is no patched version available. It is recommended to uninstall the package until a secure version is released.

How To Fix

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

npm uninstall acadgild

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