Which versions of backup3-ff are malicious?

The following npm versions of backup3-ff are flagged malicious: 1.1.2, 2.0.0. Treat any of these as compromised.

How do I remediate backup3-ff if I installed it?

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

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

Yes — backup3-ff is associated with the GHSA-8w5w-mhwr-m53r, IN-MAL-2026-010220, RLMA-2026-05498, RLUA-2026-06081 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 backup3-ff 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 backup3-ff (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging backup3-ff across your stack and pipelines.

Malicious package

backup3-ffnpm

backup3-ff is a confirmed malicious npm package (MAL-2026-10287) that steals credentials and exfiltrates sensitive data (malicious versions 1.1.2, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in backup3-ff (npm)

MAL-2026-10287

Immediate action

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

npm uninstall backup3-ff

What this malware does

The npm package [email protected] ships multiple heavily obfuscated JavaScript bundles under assets/ (AccountPage, DarkVeil, GamesPage, PlusBlockedNote, SettingsPage) using javascript-obfuscator-style hex identifiers (_0x-prefixed variable names). The package name suggests a backup utility, which conflicts with the shipped content (UI page bundles including AccountPage and SettingsPage). No traced code path is available to confirm or exclude credential harvesting, exfiltration, or remote code execution behavior inside these 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

2 flagged

1.1.22.0.0

Indicators of compromise (SHA-256)

2ecb4081ae46089d7696ee9b09726643586b21b83292f70350862c971641e7c0

9a32646e3ad3e35186f8344c19ccdecfd69c26e8047fc44b77c0516b644fd094

602f5314bb5cf2eb8e788b071e543f39c519fad7559755e74db6c22099d87ea4

73c6b415a30e53355239c6bdd8bc9233459552e5f94315f2b3c88c49e77e4cdb

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 backup3-ff (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging backup3-ff across your stack and pipelines.
If you installed it — respond
backup3-ff 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 backup3-ff 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 backup3-ff 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. backup3-ff on npm has been identified as a malicious package (versions 1.1.2, 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8w5w-mhwr-m53rIN-MAL-2026-010220RLMA-2026-05498RLUA-2026-06081

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks backup3-ff-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