Malicious Code Detected in ac1 Package - Security Alert

ac1 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13970: Malicious code in ac1 (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 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 ac1 package is an npm library designed for various functionalities within JavaScript applications. It is commonly used for its lightweight nature and ease of integration. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The ac1 package has been identified to harbor malicious code, which can lead to unauthorized access, data breaches, or other harmful actions within the applications that depend on it. This vulnerability originated from the package's codebase, which was compromised, allowing attackers to embed harmful scripts. Users of this package are at risk of exploitation, making it imperative to address this issue promptly.

How To Fix

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

npm uninstall ac1

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 avoid using the ac1 package and look for alternative libraries that provide similar functionality without the associated risks. Additionally, you can monitor your project for any suspicious activities that may arise from using this package.

Conclusion

The ac1 package has been flagged for containing malicious code, posing serious security threats to applications that utilize it. Users are strongly encouraged to remove the package and seek alternatives or update to a patched version if available. Regular monitoring and vulnerability checks are essential to maintain application security.

See every vulnerability recorded for ac1 →

Share this vulnerability

FAQ

The ac1 package is an npm library used in JavaScript applications for various functionalities, but it has recently been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify if your application is at risk.

It is advised to remove the ac1 package from your project and replace it with a secure alternative. If a patched version is released, update to that version.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Using the ac1 package can expose your application to unauthorized access, data breaches, and other security threats due to the embedded malicious code.

How To Fix

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

npm uninstall ac1

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