Malicious Code Detected in acte.js - Security Risk Alert

acte.js Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14038: Malicious code in acte.js (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 package acte.js is a JavaScript library available through the npm ecosystem, primarily used for various web development tasks. It offers functionalities that enhance the development process, but it has been identified to contain malicious code, posing a significant security risk to applications that utilize it. Users of acte.js should be aware of its vulnerabilities and take necessary precautions.

Vulnerability Detail

The vulnerability in acte.js stems from the presence of malicious code embedded within the package. This code can potentially compromise the security of applications that depend on acte.js, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall acte.js

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 acte.js in your project until a secure version is released. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The acte.js package has been identified to contain malicious code, posing a significant risk to applications that utilize it. Users are advised to remove the package and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your projects.

See every vulnerability recorded for acte.js →

Share this vulnerability

FAQ

acte.js is a JavaScript library used in web development, available through the npm package manager.

The malicious code can lead to unauthorized access and potential data breaches in applications that utilize the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

It is recommended to remove acte.js from your project and replace it with a secure alternative until a patched version is available.

As of now, there is no patched version available. Users should monitor the package repository for updates.

How To Fix

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

npm uninstall acte.js

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