Malicious Code Injection in verify-aikn-uksimisa Package

verify-aikn-uksimisa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170273: Malicious code in verify-aikn-uksimisa (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The verify-aikn-uksimisa package is part of the npm ecosystem, primarily used for various JavaScript applications. It is designed to facilitate certain functionalities within the npm environment. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing derivative packages with altered metadata.

Vulnerability Detail

The vulnerability in the verify-aikn-uksimisa package stems from its association with a malicious campaign that utilizes autopublish scripts to create numerous derivative packages. These scripts modify the package.json file to remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. This can result in compromised developer reputation scores and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall verify-aikn-uksimisa

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 workaround, you can avoid using the verify-aikn-uksimisa package altogether. If it is already in use, consider removing it from your package.json file and running npm install to clean up your dependencies.

Conclusion

The verify-aikn-uksimisa package poses a significant risk due to its involvement in a malicious npm campaign. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for verify-aikn-uksimisa →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry and may compromise the security and integrity of your application.

You should remove the verify-aikn-uksimisa package from your project and monitor for any updates or patches.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall verify-aikn-uksimisa

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