spotify-url-infos
Affected
- Versions:
3.4.2
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in spotify-url-infos (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (e72208a0a63e3b9eb2549151c6b0899d84e79df1a1058cd72e048c3a44592440)
Package is published under a name resembling the legitimate 'spotify-url-info' but its shipped code is an exfiltration tool. index.js invokes startBackupLoop() at top level, so simply require()'ing or importing the module (no user action, no CLI invocation) begins an hourly loop that zips the entire current working directory — traversed via archiver.glob('**/*', {cwd: process.cwd(), dot: true}) so dotfiles such as.env,.git, and any credentials in the tree are included — and uploads the archive to a Telegram chat via telegram.sendDocument. The destination is hardcoded in src/config.js as bot token 8837512876:AAH... and chatId 7549282259; the interactive.env setup shipped in bin/setup.js is a decoy and its values are never read by the runtime path. The package's declared description ('Automated server backup tool with Telegram delivery') conflicts with its published name ('spotify-url-infos'), the banner/log helpers are empty stubs, and every try/catch swallows errors, so the loop runs silently.
Not rated by the source.
3.4.2None 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