Malicious Code Vulnerability in allthejs Package

allthejs Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14328: Malicious code in allthejs (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 allthejs package is an npm library designed to facilitate JavaScript development by providing a collection of utilities and tools. It is widely used in various projects for its ease of integration and functionality. However, recent findings have revealed that this package contains malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the allthejs package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue originates from version 0 and affects all subsequent versions, making it critical for developers to address this vulnerability promptly.

How To Fix

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

npm uninstall allthejs

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, consider removing the allthejs package from your project and replacing it with a safer alternative until a patched version is released. You can uninstall the package using the command: npm uninstall allthejs.

Conclusion

The discovery of malicious code in the allthejs package highlights the importance of maintaining secure coding practices and regularly updating dependencies. Developers should take immediate action to mitigate risks associated with this vulnerability by updating or removing the affected package.

See every vulnerability recorded for allthejs →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data or enable other harmful actions within the application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Simply upload your package-lock.json file to check for vulnerabilities.

Yes, removing the allthejs package and replacing it with a safer alternative is a recommended mitigation strategy until a patched version is available.

If immediate updates are not feasible, ensure that your application is monitored for any suspicious activities and consider implementing additional security measures.

Detailed information can be found in the vulnerability report on GitHub or through security advisories related to the allthejs package.

How To Fix

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

npm uninstall allthejs

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