Critical Malicious Code Vulnerability in applicationooks21 Package

applicationooks21 Updated 19 Nov 2025

Summary

17/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190503: Malicious code in applicationooks21 (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 applicationooks21 package is a Node.js library designed for various application functionalities. It is utilized in numerous projects for its ease of integration and feature set. However, it has recently been identified as containing malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the applicationooks21 package. This code can compromise the integrity of any system where the package is installed, allowing unauthorized access to sensitive information, including secrets and keys. The malicious nature of the code has been confirmed by multiple sources, indicating that any system running this package should be considered fully compromised.

How To Fix

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

npm uninstall applicationooks21

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 workaround, it is recommended to uninstall the applicationooks21 package using the command: npm uninstall applicationooks21. However, be aware that simply removing the package may not eliminate all traces of the malicious code, as full control of the system may have been compromised.

Conclusion

The applicationooks21 package has been identified as containing malicious code, posing a serious security threat. Immediate action is required to remove the package and secure any sensitive information. Tools like Vulert can assist in monitoring for vulnerabilities in your applications.

See every vulnerability recorded for applicationooks21 →

Share this vulnerability

FAQ

applicationooks21 is a Node.js library used for various application functionalities, but it has been found to contain malicious code.

If you have the applicationooks21 package installed, your system is likely compromised. Use tools like Vulert to check for vulnerabilities.

Immediately uninstall the applicationooks21 package and rotate any sensitive information stored on your system.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Vulert monitors and alerts for open-source vulnerabilities in real-time using just the package-lock.json file, providing insights without needing code access.

How To Fix

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

npm uninstall applicationooks21

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