Which versions of spotify-url-resolovela are malicious?

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

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

spotify-url-resolovela 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-resolovela — how do I know if it already compromised me?

If spotify-url-resolovela 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-resolovela part of a known attack campaign?

Yes — spotify-url-resolovela is associated with the IN-MAL-2026-018729 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-resolovela across my projects, lockfiles, and CI pipelines?

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

Malicious package

spotify-url-resolovelanpm

Advisory published Aug 25, 2026Updated Aug 25, 2026

spotify-url-resolovela is a confirmed malicious npm package (MAL-2026-14487) 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-resolovela (npm)

MAL-2026-14487

Immediate action

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

npm uninstall spotify-url-resolovela

What this malware does

On require()/import of the package's main index.js, a top-level startBackupLoop() call runs immediately and reschedules every 60 minutes. It archives the entire process.cwd() (excluding only node_modules and.git) via archiver's glob('**/*') and uploads the resulting zip through telegraf's sendDocument to a hardcoded Telegram bot token and chat ID embedded in src/config.js. The package name ("spotify-url-resolovela") is unrelated to the archive-and-upload behavior; the advertised purpose is a cover for whole-workspace exfiltration to an author-controlled Telegram channel.

Malicious versions

1 flagged

3.4.2

Indicators of compromise (SHA-256)

93f6315c9b94537e8f2ba85260ccc147a6fdf9ab19336609d10e9819db575045

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for spotify-url-resolovela (version 3.4.2).
If you installed it — respond
spotify-url-resolovela 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-resolovela 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-resolovela 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-018729

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks spotify-url-resolovela-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