Which versions of backupgenuine-updated are malicious?

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

How do I remediate backupgenuine-updated if I installed it?

Remove backupgenuine-updated 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 backupgenuine-updated — how do I know if it already compromised me?

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

Yes — backupgenuine-updated is associated with the GHSA-8gjh-hmfj-xqcg, IN-MAL-2026-010226 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 backupgenuine-updated 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 backupgenuine-updated (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 backupgenuine-updated across your stack and pipelines.

Malicious package

backupgenuine-updatednpm

Malicious code in backupgenuine-updated (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10290

Immediate action

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

npm uninstall backupgenuine-updated

What this malware does

Package published as [email protected] with description "Republished package" actually contains a Vite-built single-page application titled "Lucide" that implements a Scramjet in-browser web proxy (JS/WASM assets under bfjdx/ and ct1tl/, service worker, boot module). package.json declares no lifecycle scripts (no preinstall/install/postinstall/prepare) and main points to index.html, so npm install and require() do not execute any of the shipped code on the installing machine. The shipped index.html injects a third-party script from https://c.vipersfutbol.com/script.js and the boot module hardcodes wss://21baseballacademy.com/fairs/ as the proxy transport; both only run in a browser that serves and loads the built SPA, not on the developer installing the tarball. Several bundled route chunks (AccountPage, DarkVeil, GamesPage, PlusBlockedNote, SettingsPage) are heavily obfuscated with hex-identifier naming, which is a transparency concern for the browser-side application but does not create an install-time or import-time code path on the installer.

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)

fa1560d47b61cfdcbaf0de1e41f11fed849935674ea4b18b3604158a20cdc294

163e55285112106141566338db7483490b20567a431458b4b921a71534135ce0

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 backupgenuine-updated (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 backupgenuine-updated across your stack and pipelines.
If you installed it — respond
Remove backupgenuine-updated 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 backupgenuine-updated 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 backupgenuine-updated 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. backupgenuine-updated 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-8gjh-hmfj-xqcgIN-MAL-2026-010226

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks backupgenuine-updated-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