Malicious Code Injection in lookingan-namakiki2 Package

lookingan-namakiki2 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158528: Malicious code in lookingan-namakiki2 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The lookingan-namakiki2 package is part of the npm ecosystem, often used in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages that flood the npm registry. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.

Vulnerability Detail

The vulnerability in the lookingan-namakiki2 package originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for unauthorized access to sensitive data and the compromise of application integrity.

How To Fix

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

npm uninstall lookingan-namakiki2

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 remove the lookingan-namakiki2 package from your project by executing the following command: npm uninstall lookingan-namakiki2. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The lookingan-namakiki2 package contains a serious vulnerability due to its malicious code that modifies essential files and repackages itself. It is crucial to take immediate action by updating or removing the package to protect your application from potential threats.

See every vulnerability recorded for lookingan-namakiki2 →

Share this vulnerability

FAQ

The lookingan-namakiki2 package is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file, removes private flags, and republishes variants, potentially compromising your application's security and integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you cannot update the package right away, consider uninstalling it as a temporary measure to mitigate the risk of exploitation.

You can find more information about npm vulnerabilities on the official npm website or through security advisories provided by various security organizations.

How To Fix

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

npm uninstall lookingan-namakiki2

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