Critical Malicious Code Vulnerability in dibels8-content Package

dibels8-content Updated 16 Jan 2026

Summary

16/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-279: Malicious code in dibels8-content (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 dibels8-content package is an npm library designed to provide educational content related to the DIBELS (Dynamic Indicators of Basic Early Literacy Skills) assessment. It is widely used in educational applications to facilitate literacy assessments. However, this package has been identified to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the dibels8-content package, as reported by Amazon Inspector. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The vulnerability affects all versions of the package starting from its introduction, making it critical for users to take immediate action.

How To Fix

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

npm uninstall dibels8-content

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, users can remove the dibels8-content package from their project until a secure version is released. This can be done using the command: npm uninstall dibels8-content. Additionally, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The dibels8-content package has been found to contain malicious code, posing a serious threat to applications that utilize it. Users are urged to update or remove the package to mitigate risks. Tools like Vulert can assist in monitoring and identifying vulnerabilities in real-time.

See every vulnerability recorded for dibels8-content →

Share this vulnerability

FAQ

The dibels8-content package is an npm library that provides educational content for literacy assessments based on the DIBELS framework.

The malicious code was identified by Amazon Inspector, a security assessment service that scans for vulnerabilities in software packages.

The risks include potential unauthorized access to sensitive data, data breaches, and the possibility of the application being compromised for malicious purposes.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. Simply upload your package-lock.json file to check for vulnerabilities.

Yes, Vulert allows you to monitor vulnerabilities in real-time without requiring code access or installation. You can use the Vulert playground to check your application for vulnerabilities.

How To Fix

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

npm uninstall dibels8-content

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