Malicious Code Injection in verify-aiun-misiuka Package

verify-aiun-misiuka Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170317: Malicious code in verify-aiun-misiuka (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-aiun-misiuka package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through automated publishing of derivative packages. However, it has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the verify-aiun-misiuka package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished to the npm registry. This behavior not only inflates developer reputation scores but also pollutes the npm registry with potentially harmful packages, posing risks to developers who may unknowingly install these variants.

How To Fix

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

npm uninstall verify-aiun-misiuka

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 workaround, avoid using the verify-aiun-misiuka package until a secure version is released. Regularly check for updates and consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The verify-aiun-misiuka package has been compromised with malicious code that poses significant risks to developers and their projects. Immediate action is required to remove the package and monitor for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in your software.

See every vulnerability recorded for verify-aiun-misiuka →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.

The malicious code can modify your package.json, remove private flags, and introduce potentially harmful packages into your project.

You should uninstall the verify-aiun-misiuka package immediately and monitor your project for any unusual behavior.

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

It is advisable to keep an eye on updates from the package maintainers for any patched versions that address this vulnerability.

How To Fix

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

npm uninstall verify-aiun-misiuka

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