Malicious Code Injection in nokiraine-asa: A Threat to npm Users

nokiraine-asa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162104: Malicious code in nokiraine-asa (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'nokiraine-asa' is part of the npm ecosystem, which is widely used for managing JavaScript packages. It is often utilized in various applications to enhance functionality and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through deceptive practices.

Vulnerability Detail

The vulnerability in 'nokiraine-asa' originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to security risks and compromised applications for users who unknowingly install these packages.

How To Fix

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

npm uninstall nokiraine-asa

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 an immediate workaround, you can avoid using 'nokiraine-asa' and any other packages that are part of the tea.xyz campaign. Instead, look for alternative packages that provide similar functionality without the associated risks. You can also use the following command to check for vulnerabilities in your project: 'npm audit'.

Conclusion

The 'nokiraine-asa' package poses a significant threat to npm users due to its malicious code that manipulates package metadata and pollutes the npm registry. It is crucial to take immediate action by removing the package and monitoring your dependencies for vulnerabilities to ensure the security of your applications.

See every vulnerability recorded for nokiraine-asa →

Share this vulnerability

FAQ

The 'nokiraine-asa' package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

If your application uses 'nokiraine-asa', it may be at risk of having its package.json modified and could inadvertently publish malicious variants to the npm registry.

You should uninstall the package immediately using 'npm uninstall nokiraine-asa' and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application using the Vulert playground without needing to sign up.

Yes, you should look for alternative packages that offer similar functionality but do not have the same security risks associated with them.

How To Fix

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

npm uninstall nokiraine-asa

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