Malicious Code Detected in apple-k27-project: A Critical npm Vulnerability

apple-k27-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14690: Malicious code in apple-k27-project (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 package 'apple-k27-project' is an npm package that serves various functionalities within JavaScript applications. It is designed to facilitate specific tasks, but it has been identified as containing malicious code that can compromise the integrity of applications utilizing it. This vulnerability poses a significant risk to developers and users who rely on this package for their projects.

Vulnerability Detail

The vulnerability in the 'apple-k27-project' package arises from the inclusion of malicious code that can execute harmful actions within an application. This code was introduced in version 0 and can lead to unauthorized access, data breaches, or other malicious activities. The presence of such code can severely impact the security posture of any application that incorporates this package, making it imperative 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 apple-k27-project

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 workaround, consider replacing 'apple-k27-project' with an alternative package that provides similar functionality without the associated risks. Always review the security history of any package before integrating it into your project.

Conclusion

The discovery of malicious code in the 'apple-k27-project' npm package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action to mitigate risks associated with this vulnerability by removing the affected package and considering alternatives.

See every vulnerability recorded for apple-k27-project →

Share this vulnerability

FAQ

The malicious code can execute harmful actions, potentially leading to unauthorized access or data breaches.

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

It is recommended to remove the package immediately and replace it with a safer alternative.

Currently, there is no patched version available. Users should remove the package until a secure version is released.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

How To Fix

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

npm uninstall apple-k27-project

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