Malicious Code Injection in saku-aku-iu Package: A Threat to npm Users

saku-aku-iu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165668: Malicious code in saku-aku-iu (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 saku-aku-iu package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities to inflate developer reputation scores through the creation of derivative packages.

Vulnerability Detail

The vulnerability in the saku-aku-iu package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to generate random names, often themed around Indonesian culture, and continuously republish these variants to the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to manipulate npm's ecosystem for fraudulent gains. The ramifications include potential pollution of the npm registry, loss of developer reputation, and exposure to further malicious activities.

How To Fix

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

npm uninstall saku-aku-iu

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-aku-iu package and any other packages that may be part of the same malicious campaign. To uninstall the package, run the following command in your terminal: npm uninstall saku-aku-iu.

Conclusion

The saku-aku-iu package poses a significant threat to users within the npm ecosystem due to its malicious code that modifies package metadata and repopulates the registry with harmful variants. Immediate action is required to uninstall the package and safeguard your projects from potential risks.

See every vulnerability recorded for saku-aku-iu →

Share this vulnerability

FAQ

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

This vulnerability can lead to the pollution of the npm registry and may expose your project to further malicious activities.

You should uninstall the saku-aku-iu package immediately to mitigate any risks associated with its malicious behavior.

As of now, there is no patched version available. It is recommended to remove the package entirely.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall saku-aku-iu

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