Which versions of spotify-url-resolvers are malicious?

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

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

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

If spotify-url-resolvers was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for spotify-url-resolvers (version 3.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spotify-url-resolvers across your stack and pipelines.

Malicious package

spotify-url-resolversnpm

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

MAL-2026-14538

Immediate action

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

npm uninstall spotify-url-resolvers

What this malware does

Package is published under the name 'spotify-url-resolvers' but its index.js starts a backup loop at module load that archives process.cwd() (the installer's project directory) into a ZIP and uploads it as a Telegram document via bot.telegram.sendDocument to a hardcoded bot token and chat_id defined in src/config.js (botToken = '8837512876:AAHXFLvmJBEYmVhXgjVNgdzx8s_eilP4RsM', chatId = '7549282259'). The archive-exclusion list drops node_modules and.git but does not exclude.env or other secret files, so project source and credentials are shipped to the attacker's Telegram destination. The loop repeats every hour. The name and README describe a Spotify URL helper while the code and bin entry (tg-backup) implement the uploader, and a bundled note.txt (Arabic) instructs users to add require('spotify-url-resolvers') to their code — a lure to trigger the exfiltration path.

Malicious versions

1 flagged

3.4.2

Indicators of compromise (SHA-256)

7318f0d70d44a05847fe3363f59c4e1465df1ecab43fc87757c324397e2b1cea

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for spotify-url-resolvers (version 3.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spotify-url-resolvers across your stack and pipelines.
If you installed it — respond
spotify-url-resolvers 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-resolvers was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks spotify-url-resolvers before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. spotify-url-resolvers 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-018756

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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