Which versions of spotify-url-infos are malicious?

The following npm versions of spotify-url-infos are flagged malicious: 3.4.2. Treat any of these as compromised.

How do I remediate spotify-url-infos if I installed it?

spotify-url-infos is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed spotify-url-infos — how do I know if it already compromised me?

If spotify-url-infos was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is spotify-url-infos part of a known attack campaign?

Yes — spotify-url-infos is associated with the IN-MAL-2026-018738 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find spotify-url-infos across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for spotify-url-infos (version 3.4.2).

Malicious package

spotify-url-infosnpm

Advisory published Aug 25, 2026Updated Aug 25, 2026

spotify-url-infos is a confirmed malicious npm package (MAL-2026-14492) that steals credentials and exfiltrates sensitive data (malicious version 3.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in spotify-url-infos (npm)

MAL-2026-14492

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall spotify-url-infos

What this malware does

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.

Malicious versions

1 flagged

3.4.2

Indicators of compromise (SHA-256)

e72208a0a63e3b9eb2549151c6b0899d84e79df1a1058cd72e048c3a44592440

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for spotify-url-infos (version 3.4.2).
If you installed it — respond
spotify-url-infos is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If spotify-url-infos was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. spotify-url-infos on npm has been identified as a malicious package (version 3.4.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018738

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks spotify-url-infos-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database