Which versions of backup2-asd are malicious?

The following npm versions of backup2-asd are flagged malicious: 2.0.0. Treat any of these as compromised.

How do I remediate backup2-asd if I installed it?

Remove backup2-asd from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed backup2-asd — how do I know if it already compromised me?

If backup2-asd 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 backup2-asd part of a known attack campaign?

Yes — backup2-asd is associated with the GHSA-5wxc-4vm4-55cx, IN-MAL-2026-010225 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 backup2-asd 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 backup2-asd (version 2.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging backup2-asd across your stack and pipelines.

Malicious package

backup2-asdnpm

backup2-asd is a confirmed malicious npm package (MAL-2026-10286) that executes malicious code on install (malicious version 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in backup2-asd (npm)

MAL-2026-10286

Immediate action

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

npm uninstall backup2-asd

What this malware does

The tarball published as [email protected] is a Vite-built browser application (branded 'Lucide') rather than a Node library. package.json declares main as index.html and defines no lifecycle scripts (no preinstall/install/postinstall/prepare), so npm install and require() do not execute any code in the installer's Node process. The bundled assets include heavily obfuscated JavaScript (AccountPage, DarkVeil, GamesPage, PlusBlockedNote, SettingsPage) and third-party components (Scramjet in-browser HTTP proxy via service worker, libcurl.js, LiveKit, fingerprinting, chat/games/AI pages); index.html loads an external script from c.vipersfutbol.com and Google Tag Manager. The package name and description ('Republished package') do not match the shipped browser-app contents. Behavior affects end-users who visit a site built from these assets, not the developer who installs the tarball.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

7ecf4d86a048d508520443a6e65887eef3dfd9dc133f10af2a3a6f81cd496946

a6fe96add7d70ce5933988f1c78b934187e279d88618bd3f211de3d719177168

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for backup2-asd (version 2.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging backup2-asd across your stack and pipelines.
If you installed it — respond
Remove backup2-asd from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If backup2-asd 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 backup2-asd 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. backup2-asd on npm has been identified as a malicious package (version 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5wxc-4vm4-55cxIN-MAL-2026-010225

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks backup2-asd-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database