Malicious Code Injection in saku-aimau-umilakoi: A Threat to npm Users

saku-aimau-umilakoi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165630: Malicious code in saku-aimau-umilakoi (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

saku-aimau-umilakoi is an npm package that has been implicated in a malicious campaign targeting the npm registry. It is part of a broader initiative associated with the tea.xyz token reward program, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This package, like others in the campaign, is designed to manipulate the npm ecosystem for malicious purposes.

Vulnerability Detail

The vulnerability in saku-aimau-umilakoi arises from its inclusion in a malicious package ecosystem that 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 these variants, effectively polluting the npm registry and potentially compromising the integrity of applications that depend on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall saku-aimau-umilakoi

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 saku-aimau-umilakoi package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity and source of any package before including it in your project.

Conclusion

The saku-aimau-umilakoi package poses a significant risk due to its malicious behavior linked to the tea.xyz token reward campaign. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security and integrity of their applications.

See every vulnerability recorded for saku-aimau-umilakoi →

Share this vulnerability

FAQ

saku-aimau-umilakoi is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and its dependencies.

You should uninstall the saku-aimau-umilakoi package immediately and check for any other affected packages in your project.

There is no patch for the saku-aimau-umilakoi package itself, as it is recommended to remove it entirely from your project.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software.

How To Fix

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

npm uninstall saku-aimau-umilakoi

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