Malicious Code Detected in androidsc Package - Security Alert

androidsc Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14507: Malicious code in androidsc (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 androidsc package is an npm library designed for Android development, offering various functionalities to streamline the development process. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize this package. Users of this package should be aware of its vulnerabilities and take necessary precautions.

Vulnerability Detail

The vulnerability in the androidsc package stems from the inclusion of malicious code that can compromise the security of applications using it. This code may lead to unauthorized access, data breaches, or other malicious activities. The vulnerability was introduced in version 0 and affects all subsequent versions, making it critical for users to address this issue promptly.

How To Fix

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

npm uninstall androidsc

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 measure, if you cannot update the package immediately, consider removing the androidsc package from your project until a secure version is released. You can do this by executing: 'npm uninstall androidsc'.

Conclusion

The androidsc package has been identified to contain malicious code, posing serious security risks to applications that utilize it. Users are strongly advised to update the package as soon as a patched version is available or to uninstall it temporarily to protect their applications.

See every vulnerability recorded for androidsc →

Share this vulnerability

FAQ

The androidsc package is an npm library used for Android development, providing various tools and functionalities for developers.

The malicious code can lead to unauthorized access and potential data breaches, compromising the security of applications that utilize the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

As of now, there is no patched version available. Users should monitor the package repository for updates and security advisories.

If you cannot update the androidsc package right away, consider uninstalling it from your project to mitigate security risks.

How To Fix

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

npm uninstall androidsc

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