Which versions of backup4-gasp are malicious?

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

How do I remediate backup4-gasp if I installed it?

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

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

Yes — backup4-gasp is associated with the GHSA-rwpw-7393-4jg2, IN-MAL-2026-010222 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 backup4-gasp 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 backup4-gasp (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 backup4-gasp across your stack and pipelines.

Malicious package

backup4-gaspnpm

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

MAL-2026-10288

Immediate action

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

npm uninstall backup4-gasp

What this malware does

The package ships multiple heavily obfuscated JavaScript bundles under assets/ (AccountPage, DarkVeil, GamesPage, PlusBlockedNote, SettingsPage) that use hex-prefixed identifier mangling consistent with javascript-obfuscator output. The package name presents as a backup utility, but the shipped assets appear to be a bundled web UI (account, settings, games pages) whose contents cannot be readily inspected due to the obfuscation. No install-time lifecycle hook, hardcoded network destination, credential access path, or dropper mechanism was identified in the shipped files. The mismatch between the declared name and the shipped web-app assets, combined with opaque obfuscation of user-facing code paths, reduces transparency about what the bundles do when loaded.

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)

941983b0216e3cae217e1472fd7c51d949b0ad611f39133f94d32cdd27f6dd87

8e42991a6cdb40d2c1dec58317f280d0a6e38ad2dfa14b1a0dfe2ac40c5dc18a

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 backup4-gasp (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 backup4-gasp across your stack and pipelines.
If you installed it — respond
backup4-gasp 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 backup4-gasp 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 backup4-gasp 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. backup4-gasp 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-rwpw-7393-4jg2IN-MAL-2026-010222

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks backup4-gasp-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