Malicious Code Detected in almworks Package: Security Alert

almworks Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14338: Malicious code in almworks (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 almworks package is an npm library that is utilized for various functionalities in JavaScript applications. It is designed to enhance productivity and streamline workflows for developers. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that rely on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the almworks package. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in all versions starting from 0, making it critical for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall almworks

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, it is advisable to remove the almworks package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall almworks'. This will help mitigate the risk of exposure to the malicious code.

Conclusion

The discovery of malicious code in the almworks package highlights the importance of maintaining vigilance regarding open-source dependencies. Users are encouraged to update or remove the package to safeguard their applications against potential threats.

See every vulnerability recorded for almworks →

Share this vulnerability

FAQ

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

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities. By analyzing your package-lock.json file, Vulert can help you identify if your application is affected.

Yes, Vulert provides real-time monitoring for open-source vulnerabilities without requiring code access or installation. You can check your application's status using the Vulert playground.

If immediate updates are not possible, consider removing the package from your project as a temporary measure to avoid exposure to the malicious code.

Detailed information about the vulnerability can be found on the GitHub repository of the malicious packages, specifically at the provided source link.

How To Fix

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

npm uninstall almworks

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