Malicious Code Vulnerability in un112 Package - npm

un112 Updated 22 Jan 2026

Summary

22/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-459: Malicious code in un112 (npm). Affects un112 versions 1.0.18 – 1.0.5. 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 'un112' package is a JavaScript library available through npm, primarily used for various utility functions in Node.js applications. Despite its intended functionality, the package has been identified as malicious, posing significant risks to users and their applications. This vulnerability arises from the package's ability to communicate with domains linked to malicious activities and execute harmful commands.

Vulnerability Detail

The vulnerability in the 'un112' package stems from its malicious design, which includes communication with a domain associated with harmful activities. The package executes commands that can compromise the security of the host system, potentially leading to unauthorized access, data breaches, or further exploitation of the affected environment. This vulnerability was identified by the OpenSSF Package Analysis project, which flagged version 1.0.18 as malicious due to its behavior.

How To Fix

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

npm uninstall un112

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 specific workarounds to mitigate the risks posed by the 'un112' package. The best course of action is to uninstall the package and seek alternative libraries that do not exhibit malicious behavior.

Conclusion

The 'un112' package has been identified as malicious, posing significant risks to users and their applications. It is crucial to uninstall this package and seek alternatives to ensure the security of your software. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the integrity of your applications.

See every vulnerability recorded for un112 →

Share this vulnerability

FAQ

The 'un112' package is a JavaScript utility library available on npm, designed for various functions in Node.js applications.

The malicious behavior was identified by the OpenSSF Package Analysis project, which flagged the package for communicating with malicious domains and executing harmful commands.

If you have 'un112' installed, you should uninstall it immediately and look for alternative packages that provide similar functionality without the associated risks.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities without any signup using the Vulert playground.

No, the latest version (1.0.18) has been flagged as malicious. It is recommended to remove the package entirely.

How To Fix

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

npm uninstall un112

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