Malicious Code Detected in verify-aiun-miska: A Threat to npm Users

verify-aiun-miska Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170318: Malicious code in verify-aiun-miska (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 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 package 'verify-aiun-miska' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages with altered names and metadata. The malicious nature of this package poses a significant risk to developers and users relying on npm for their projects.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the 'verify-aiun-miska' package, which is linked to a broader campaign that floods the npm registry with fake packages. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby inflating developer reputation scores for token rewards. The continuous republishing of these variants can lead to registry pollution, making it difficult for developers to find legitimate packages.

How To Fix

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

npm uninstall verify-aiun-miska

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, avoid using the 'verify-aiun-miska' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your project's dependencies to ensure they are secure.

Conclusion

The 'verify-aiun-miska' package poses a significant threat to npm users due to its malicious code designed to exploit the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for verify-aiun-miska →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.

You should uninstall the 'verify-aiun-miska' package immediately and audit your other dependencies for vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring an account.

How To Fix

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

npm uninstall verify-aiun-miska

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