Malicious Code Injection in siska-tiwul89-apidev: A Threat to npm Packages

siska-tiwul89-apidev Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90678: Malicious code in siska-tiwul89-apidev (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 package 'siska-tiwul89-apidev' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in 'siska-tiwul89-apidev' stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous publication of derivative packages, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can affect developers by inflating reputation scores fraudulently and may lead to the installation of compromised packages.

How To Fix

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

npm uninstall siska-tiwul89-apidev

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, avoid using the 'siska-tiwul89-apidev' package and monitor your dependencies for any signs of malicious activity. You can also use tools like Vulert to check your application for vulnerabilities without needing to access the code directly.

Conclusion

The 'siska-tiwul89-apidev' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can provide additional security by alerting you to potential threats in real-time.

See every vulnerability recorded for siska-tiwul89-apidev →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.

You can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without needing to install any software.

You should uninstall the package immediately and check your project for any other potentially compromised dependencies.

Yes, tools like Vulert can help you monitor and alert you to open-source vulnerabilities in your software.

Failing to address this vulnerability can lead to compromised project integrity, fraudulent reputation inflation, and potential security risks for users.

How To Fix

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

npm uninstall siska-tiwul89-apidev

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