Malicious Code Vulnerability in abukarim Package: Exploitation of npm Registry

abukarim Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170644: Malicious code in abukarim (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The abukarim package is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to share and manage code libraries. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts designed to manipulate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the abukarim package stems from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages.

How To Fix

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

npm uninstall abukarim

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 abukarim package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The abukarim package poses a significant risk due to its malicious code that manipulates the npm registry. It is crucial for developers to remove this package from their projects and monitor for any future updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications.

See every vulnerability recorded for abukarim →

Share this vulnerability

FAQ

The abukarim package is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, which may compromise the integrity of other packages and affect your project's reliability.

You should uninstall the abukarim package immediately using the command npm uninstall abukarim and check for any dependencies that may be affected.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application against known vulnerabilities at Vulert Scanner.

Currently, it is recommended to remove the package. If a patched version becomes available in the future, you can update it using npm update abukarim.

How To Fix

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

npm uninstall abukarim

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