Malicious code in lockself (npm)

lockself Updated 02 Oct 2025

Summary

28/12/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8757: Malicious code in lockself (npm). Affects lockself versions 1.0.0 – 2.0.0. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The lockself package is an npm package that is used for locking a computer's screen. It provides a simple way to prevent unauthorized access to a computer by requiring a password to unlock the screen. The package is commonly used in various applications and systems to enhance security. However, the lockself 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 lockself package has been compromised, and any computer with this package installed or running should be considered fully compromised. The malicious code within the package can give complete control of the computer to an outside entity. As a result, all secrets and keys stored on the affected computer should be rotated immediately from a different computer. Simply removing the package may not 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 lockself

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. The recommended course of action is to follow the steps outlined in the 'how_to_fix' section.

Conclusion

The lockself package has been found to contain malicious code, posing a significant security risk to any computer with it installed or running. It is crucial to take immediate action by rotating all secrets and keys, removing the package, conducting a security audit, and implementing additional security measures. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for lockself →

Share this vulnerability

FAQ

The lockself package is an npm package used for locking a computer's screen to prevent unauthorized access.

The lockself package provides a simple way to require a password to unlock a computer's screen, enhancing security.

The lockself package vulnerability can result in a complete compromise of the affected computer, giving control to an outside entity. This can lead to unauthorized access to sensitive data and potential misuse of the compromised system.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability without requiring access to the code or installation. Simply provide your package-lock.json file to the playground.

For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.

How To Fix

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

npm uninstall lockself

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