Critical Malicious Code Vulnerability in @wgu-edu/wgu-core Package

@wgu-edu/wgu-core Updated 06 Mar 2026

Summary

06/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1269: Malicious code in @wgu-edu/wgu-core (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 @wgu-edu/wgu-core package is a JavaScript library used within the npm ecosystem, primarily designed for educational applications. It provides various functionalities that support the development of web applications. However, this package has been identified to contain 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 @wgu-edu/wgu-core package. This code can compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has inserted harmful code into the package, making it a serious threat to users and their data.

How To Fix

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

npm uninstall @wgu-edu/wgu-core

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

There are no effective workarounds for this vulnerability other than removing the package and securing your system. Ensure that all sensitive information is rotated and that your system is monitored for any unusual activity.

Conclusion

The @wgu-edu/wgu-core package contains a critical vulnerability due to embedded malicious code. Immediate action is required to uninstall the package and secure your system. Regular monitoring and vulnerability checks are essential to maintain the integrity of your applications.

See every vulnerability recorded for @wgu-edu/wgu-core →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information stored on your system.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

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

Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete compromise of your system.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, ensuring your applications remain secure.

How To Fix

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

npm uninstall @wgu-edu/wgu-core

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