Malicious code in @homelte_dev/frontend (npm)

@homelte_dev/frontend Updated 02 Oct 2025

Summary

13/10/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8375: Malicious code in @homelte_dev/frontend (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 @homelte_dev/frontend package is an npm package used for frontend development. It provides various functionalities and components for building user interfaces. However, this package has been found to contain malicious code, which poses a significant security risk to any computer that has it installed or running.

Vulnerability Detail

The malicious code in @homelte_dev/frontend has been identified as a serious security threat. It is recommended to consider any computer with this package installed as fully compromised. The code may grant outside entities full control of the computer, potentially exposing all secrets and keys stored on it. Immediate action is required to rotate all affected credentials from a different computer. While removing the package is advised, it cannot guarantee the removal of all malicious software resulting from its installation.

How To Fix

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

npm uninstall @homelte_dev/frontend

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

There is no specific workaround mentioned for this vulnerability. It is crucial to follow the recommended steps for fixing the issue.

Conclusion

The @homelte_dev/frontend package has been found to contain malicious code, posing a significant security risk. It is crucial to take immediate action to rotate affected credentials, remove the package, and conduct a thorough security audit. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for @homelte_dev/frontend →

Share this vulnerability

FAQ

The impact of this vulnerability is severe, as it can compromise the security of the affected computer and expose sensitive information.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your computer is affected by this vulnerability. It analyzes the package-lock.json file to identify vulnerabilities in your software.

While removing the @homelte_dev/frontend package is recommended, it may not completely remove all malicious software installed as a result of its presence. A thorough security audit is necessary to ensure complete remediation.

If your computer is compromised, it is crucial to rotate all secrets and keys stored on it from a different, secure computer. Additionally, conduct a security audit to identify and remove any remaining malicious software.

To prevent similar vulnerabilities, it is important to regularly update and patch all software components, including npm packages. Additionally, consider using vulnerability monitoring tools like Vulert to receive real-time alerts for open-source vulnerabilities.

How To Fix

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

npm uninstall @homelte_dev/frontend

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