Malicious Code Injection in lookingan-nakomi9 Package

lookingan-nakomi9 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158415: Malicious code in lookingan-nakomi9 (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 lookingan-nakomi9 package is part of the npm ecosystem, often utilized in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that manipulate developer reputation scores. This package, like others in the campaign, is designed to automatically generate and publish derivative packages, potentially compromising the integrity of applications that depend on it.

Vulnerability Detail

The vulnerability in the lookingan-nakomi9 package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to a polluted npm registry. The malicious payload can cause significant issues, including the unintentional exposure of sensitive information and the introduction of unstable or harmful code into dependent applications.

How To Fix

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

npm uninstall lookingan-nakomi9

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, you can prevent the installation of the lookingan-nakomi9 package by using npm's package-lock.json file to monitor dependencies. Ensure that your package-lock.json does not include this package, and regularly audit your dependencies for any malicious code.

Conclusion

The lookingan-nakomi9 package poses a significant risk due to its malicious code that alters package metadata and can compromise application integrity. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for lookingan-nakomi9 →

Share this vulnerability

FAQ

The lookingan-nakomi9 package is an npm package associated with the tea.xyz token reward campaign, which is known for flooding the npm registry with malicious packages.

The malicious code modifies your package.json file, potentially exposing sensitive information and introducing unstable code into your application.

You should uninstall the package immediately using the command npm uninstall lookingan-nakomi9 and check for any other affected packages.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall lookingan-nakomi9

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