@sql-access/nodesql
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-qpx3-6fx4-259q
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in @sql-access/nodesql (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (2acee7592879b9eab377fb8e97a1fa2949b298f4418d37fb963e157971638c90)
@sql-access/[email protected] is a decoy package whose identity, README, and code do not match. The package name and keywords advertise SQL/Node functionality; the README is copy-pasted from an unrelated 'bare-stream' streaming library and points to github.com/guilderguzman/sql-link; index.js is a verbatim copy of the feross/buffer Buffer polyfill. A single statement has been injected as the first executable line of index.js: import('@sqlite-node/createsql');. As a result, any consumer that does require('@sql-access/nodesql') will asynchronously load and execute the top-level code of @sqlite-node/createsql, an unpinned (^1.0.5) separately-published package in an attacker-namespaced scope that has no relationship to a Buffer polyfill or to the package's stated SQL purpose. The decoy code itself performs no SQL work, no Buffer functionality is reached by the consumer in any meaningful way, and the only practical effect of installing or requiring this package is to silently pull a different, attacker-controlled module into the installer's dependency graph and execute it at import time. The combined identity confusion (name/README/code mismatch), namesquat-shaped transitive (@sqlite-node/createsql), unpinned caret range, and bolt-on dynamic import injected into otherwise-pristine upstream source match the documented loader/decoy supply-chain pattern.
Source: ghsa-malware (8d81e63498460519da77090ce672f258da8fc5ebc304a472b695b0b5475a079e)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0