Critical Malicious Code Vulnerability in worldnormal Package

worldnormal Updated 21 Jan 2026

Summary

21/01/2026

Disclosed on

CRITICAL

Severity

No i

Fix available

Critical

Severity

Not published

CVSS Score

MAL-2026-403: Malicious code in worldnormal (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 Browse

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.

Background

The worldnormal package is an npm library designed for various functionalities within JavaScript applications. It is commonly used for managing and manipulating data in web applications. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, making it a significant threat to developers and users alike.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the worldnormal package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to the package's malicious intent, as identified by the GitHub Security Advisory (GHSA-h55w-3xx5-rm4c). The ramifications include potential data breaches and loss of control over the affected systems, as removing the package may not eliminate all malicious software introduced by its installation.

How To Fix

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

npm uninstall worldnormal

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 worldnormal package. The only recommended action is to uninstall the package and secure your system.

Conclusion

The worldnormal package has been identified as containing malicious code that poses a severe security risk to any system it is installed on. Immediate uninstallation and rotation of sensitive information are necessary to mitigate this threat. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for worldnormal →