Malicious Code Injection in lookingan-namakiki55: A Threat to npm Packages

lookingan-namakiki55 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158567: Malicious code in lookingan-namakiki55 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'lookingan-namakiki55' is part of a broader campaign targeting npm, designed to exploit the npm registry by flooding it with malicious packages. These packages often contain scripts that automate the creation and publication of derivative packages, which can mislead developers and inflate reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and continuously republish variants, thereby polluting the npm ecosystem.

Vulnerability Detail

The vulnerability in 'lookingan-namakiki55' originates from its association with the tea.xyz token reward campaign. It includes scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall lookingan-namakiki55

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 use the following command to prevent the installation of this malicious package in the future: 'npm install --no-optional'. This command will ensure that optional dependencies, which may include malicious packages, are not installed.

Conclusion

The 'lookingan-namakiki55' package poses a significant threat to the integrity of npm packages due to its malicious behavior. It is essential for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can further enhance your ability to monitor and manage vulnerabilities in your applications.

See every vulnerability recorded for lookingan-namakiki55 →

Share this vulnerability

FAQ

'lookingan-namakiki55' is an npm package identified as part of a malicious campaign to exploit the npm registry by flooding it with harmful packages.

If 'lookingan-namakiki55' is installed, it can modify your package.json file and republish variants, potentially leading to security vulnerabilities in your application.

You should uninstall 'lookingan-namakiki55' immediately using 'npm uninstall lookingan-namakiki55' and check your package-lock.json for any references to it.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner without any signup.

Yes, tools like Vulert can help you monitor and alert for open-source vulnerabilities in your software, ensuring that you stay informed about potential risks.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall lookingan-namakiki55

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