Malicious Code Injection in verify-ain-ukasi Package

verify-ain-ukasi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170308: Malicious code in verify-ain-ukasi (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 verify-ain-ukasi package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages designed to manipulate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the verify-ain-ukasi package stems from its malicious code that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, particularly themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for unauthorized access to sensitive data and the compromise of application integrity.

How To Fix

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

npm uninstall verify-ain-ukasi

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 measure, you can prevent the installation of this package by using npm's 'npm audit' command to identify vulnerabilities in your dependencies and address them accordingly. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities without requiring code access.

Conclusion

The verify-ain-ukasi package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry with harmful variants. It is crucial to remove this package and monitor your project for vulnerabilities to maintain application security.

See every vulnerability recorded for verify-ain-ukasi →

Share this vulnerability

FAQ

The verify-ain-ukasi package is an npm package that has been identified as malicious, designed to manipulate developer reputation scores through automated publishing of harmful variants.

This vulnerability can compromise your application's integrity by introducing malicious code that modifies essential files and potentially exposes sensitive data.

If you have installed the verify-ain-ukasi package, you should uninstall it immediately using 'npm uninstall verify-ain-ukasi' and review your dependencies for any other malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access. You can also check your application using the Vulert playground.

To prevent similar vulnerabilities, regularly audit your dependencies using 'npm audit', keep your packages updated, and utilize monitoring tools like Vulert.

How To Fix

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

npm uninstall verify-ain-ukasi

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