Which versions of backup-my-data are malicious?

The following npm versions of backup-my-data are flagged malicious: 1.0.1, 1.0.2, 1.0.9. Treat any of these as compromised.

How do I remediate backup-my-data if I installed it?

backup-my-data 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 backup-my-data — how do I know if it already compromised me?

If backup-my-data 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 backup-my-data part of a known attack campaign?

Yes — backup-my-data is associated with the IN-MAL-2026-005663, IN-MAL-2026-005665, IN-MAL-2026-005664 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 backup-my-data 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 backup-my-data (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging backup-my-data across your stack and pipelines.

Malicious package

backup-my-datanpm

backup-my-data is a confirmed malicious npm package (MAL-2026-5603) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2, 1.0.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in backup-my-data (npm)

MAL-2026-5603

Immediate action

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

npm uninstall backup-my-data

What this malware does

The package's collect.js loads child_process, fs, os, http and https, gathers host identifiers via os.hostname() and os.homedir(), enumerates filesystem paths via fs.existsSync, and POSTs the collected data to the hardcoded endpoint http://aab.sportsontheweb.net (collect.js line 13, POST at line 366). The package's stated purpose ('backup-my-data') is a cover; the runtime behavior is system-information harvesting and exfiltration to an attacker-controlled host that has no relationship to the package name or any documented backup service. Installing or loading this package leaks host identity and filesystem reconnaissance data to a third-party endpoint.

Malicious versions

3 flagged

1.0.11.0.21.0.9

Indicators of compromise (SHA-256)

3184167d3b1cd30c17f285b5bc511295b55de4b37de52a228cda9f1b80044247

909d29560b504f0b737cee3d66f3b32cc61931824e7547c44fb1b30d4958c427

de638457ace180ab303f4002aa27d9560f2caf6c8f28d04ba5521486d65d34b6

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

Campaign

IN-MAL-2026-005663IN-MAL-2026-005665IN-MAL-2026-005664

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks backup-my-data-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