CVE-2017-16049: Hijacked Environment Variables in nodesqlite

nodesqlite Updated 02 Oct 2025

Summary

23/07/2018
No i
High
7.5

CVE-2017-16049: nodesqlite is malware. Affects nodesqlite versions < 1.0.2. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The nodesqlite package is an npm package that provides a SQLite database driver for Node.js applications. It allows developers to interact with SQLite databases using JavaScript. However, all versions of the nodesqlite package have been found to contain malware that steals environment variables and sends them to attacker-controlled locations.

Vulnerability Detail

The vulnerability in the nodesqlite package allows an attacker to hijack environment variables and exfiltrate them to their own servers. This can lead to the compromise of sensitive information such as credentials, tokens, and other sensitive data stored in environment variables. The package has been unpublished from the npm registry to prevent further installations.

How To Fix

No fixed version is published for this vulnerability.

If you have the nodesqlite package installed in your environment, it is recommended to take the following steps to remediate the vulnerability:

  1. Delete the nodesqlite package from your project.
  2. Clear your npm cache to ensure the package is not reinstalled.
  3. Check for any other occurrences of the nodesqlite package in your project's package.json files and remove them.
  4. Regenerate any sensitive credentials that may have been exposed, such as registry credentials, tokens, and database credentials stored in environment variables.
  5. Review any services that may have been exposed via compromised credentials for indicators of compromise.

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 for this vulnerability. The recommended course of action is to follow the steps mentioned in the 'how_to_fix' section to remove the nodesqlite package and mitigate the risk.

Conclusion

The nodesqlite package has been found to contain malware that steals environment variables. If you have this package installed in your environment, it is crucial to take immediate action to remove it and mitigate the risk of credential compromise. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for nodesqlite →

Share this vulnerability

FAQ

You can check if the nodesqlite package is installed in your environment by running the command 'npm ls nodesqlite' in your project directory. If the package is installed, it will be listed in the output.

If you find the nodesqlite package installed in your environment, it is recommended to follow the steps mentioned in the 'how_to_fix' section to remove the package and mitigate the vulnerability.

To clear your npm cache, you can run the command 'npm cache clean --force' in your terminal or command prompt.

If you suspect your credentials have been compromised, it is recommended to regenerate those credentials immediately. This includes registry credentials, tokens, and any other sensitive credentials stored in environment variables.

To review services for indicators of compromise, you should analyze logs, monitor network traffic, and look for any suspicious activity or unauthorized access. It is also recommended to consult with a security professional for a thorough investigation.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

No fixed version is published for this vulnerability.

If you have the nodesqlite package installed in your environment, it is recommended to take the following steps to remediate the vulnerability:

  1. Delete the nodesqlite package from your project.
  2. Clear your npm cache to ensure the package is not reinstalled.
  3. Check for any other occurrences of the nodesqlite package in your project's package.json files and remove them.
  4. Regenerate any sensitive credentials that may have been exposed, such as registry credentials, tokens, and database credentials stored in environment variables.
  5. Review any services that may have been exposed via compromised credentials for indicators of compromise.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.