Critical Malicious Code Vulnerability in waojpf Package

waojpf Updated 19 Oct 2026

Summary

19/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-18039: Malicious code in waojpf (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The waojpf package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers to streamline certain processes. However, this package has been identified as containing malicious code, posing significant risks to any system where it is installed. Users of waojpf should be aware of its potential to compromise sensitive data and system integrity.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the waojpf package. This code can grant unauthorized access to an attacker, allowing them to control the affected system fully. As a result, any secrets or keys stored on the compromised machine should be considered at risk. The origin of this issue is linked to the package's malicious nature, which has been confirmed by security researchers. The ramifications include potential data breaches, unauthorized data access, and complete system compromise.

How To Fix

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

npm uninstall waojpf

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

Currently, there are no effective workarounds to mitigate the risks posed by the waojpf package. The only recommended action is to uninstall the package entirely.

Conclusion

The waojpf package poses a serious security threat due to the embedded malicious code. Users must take immediate action to uninstall the package and secure their systems. Regular monitoring for vulnerabilities is essential to maintain the integrity of your applications.

See every vulnerability recorded for waojpf →

Share this vulnerability

FAQ

The waojpf package is an npm library used in JavaScript applications, but it has been identified as containing malicious code.

The malicious code can grant attackers full control over your system, leading to potential data breaches and unauthorized access.

You should uninstall the waojpf package immediately and rotate any sensitive keys or secrets stored on your system.

No, there is currently no patched version available for the waojpf package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall waojpf

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