Malicious Code Injection in nokire-abimanyu68 Package

nokire-abimanyu68 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162184: Malicious code in nokire-abimanyu68 (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 nokire-abimanyu68 package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses significant risks to the integrity of the npm registry and the security of applications relying on these packages.

Vulnerability Detail

The vulnerability in the nokire-abimanyu68 package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising applications that depend on these packages. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.

How To Fix

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

npm uninstall nokire-abimanyu68

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 the nokire-abimanyu68 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies to ensure that no malicious packages are included in your project.

Conclusion

The nokire-abimanyu68 package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is essential to remove this package and monitor your dependencies to maintain the security of your applications.

See every vulnerability recorded for nokire-abimanyu68 →

Share this vulnerability

FAQ

The nokire-abimanyu68 package is part of a series of npm packages linked to a token reward campaign, designed to inflate developer reputation scores.

The malicious code modifies your package.json file and can lead to the pollution of the npm registry, potentially compromising your application's security.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground.

You should uninstall the package immediately and audit your dependencies to ensure no other malicious packages are present.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.

How To Fix

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

npm uninstall nokire-abimanyu68

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