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

lookingan-namakiki28 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158537: Malicious code in lookingan-namakiki28 (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 package 'lookingan-namakiki28' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automatically generate and publish derivative versions with randomized names, aiming to inflate developer reputation scores for token rewards. This behavior raises significant concerns regarding the integrity and security of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'lookingan-namakiki28' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This results in a pollution of the npm registry with numerous derivative packages, potentially leading to confusion and misuse by developers who may unknowingly install these compromised packages. The origin of this vulnerability is linked to a broader trend of malicious packages flooding the npm ecosystem, specifically targeting developers seeking rewards through the tea protocol.

How To Fix

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

npm uninstall lookingan-namakiki28

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 avoid using this package by ensuring that your project does not include it in your dependencies. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'lookingan-namakiki28' package poses a significant risk due to its malicious behavior of generating and publishing compromised packages. It is essential for developers to be vigilant and remove such packages from their projects to maintain the security and integrity of their applications. Utilizing tools like Vulert can aid in monitoring and identifying vulnerabilities in real-time.

See every vulnerability recorded for lookingan-namakiki28 →

Share this vulnerability

FAQ

'lookingan-namakiki28' is an npm package associated with a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.

The vulnerability can lead to the installation of malicious packages that may compromise your project's integrity and security.

You should immediately uninstall 'lookingan-namakiki28' from your project to mitigate any potential risks.

Yes, tools like Vulert can help monitor your package-lock.json for open-source vulnerabilities in real-time.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall lookingan-namakiki28

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