Which versions of backup5-updated are malicious?

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

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

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

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

Yes — backup5-updated is associated with the GHSA-cjhm-8r3j-gcvx, IN-MAL-2026-010227 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 backup5-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 backup5-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 backup5-updated across your stack and pipelines.

Malicious package

backup5-updatednpm

backup5-updated is a confirmed malicious npm package (MAL-2026-10289) that steals credentials and exfiltrates sensitive data (malicious version 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in backup5-updated (npm)

MAL-2026-10289

Immediate action

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

npm uninstall backup5-updated

What this malware does

The package tarball contains multiple heavily obfuscated JavaScript bundles under assets/ (AccountPage, DarkVeil, GamesPage, PlusBlockedNote, SettingsPage), each using hex-prefixed identifier obfuscation typical of javascript-obfuscator output. These files appear to be a bundled web application (page components and UI assets) rather than a Node library entry point. No lifecycle scripts, install-time execution, credential access, or network destinations were identified in the reviewed content, and no top-level require/import side effects into these obfuscated bundles were traced. The obfuscation itself hides the actual runtime behavior of the shipped assets, so intent cannot be confirmed from the file structure alone. The package name presents as a backup utility, which is inconsistent with the shipped content (frontend page bundles).

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)

143e6a37fc9e54277ccc4384f43700e96c850774c1cff47c34348cbd67963aa0

0fbc0dc5fea4212458853e895b9b9df474401727a4768f47e3016a8c871fd5c7

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 backup5-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 backup5-updated across your stack and pipelines.
If you installed it — respond
backup5-updated 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 backup5-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 backup5-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. backup5-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-cjhm-8r3j-gcvxIN-MAL-2026-010227

References

Credits

Amazon Inspector · finder

Detect & block this

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