Which versions of backpack-ios are malicious?

The following npm versions of backpack-ios are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate backpack-ios if I installed it?

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

If backpack-ios was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is backpack-ios part of a known attack campaign?

Yes — backpack-ios is associated with the IN-MAL-2026-007413 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 backpack-ios across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for backpack-ios (version 1.0.0).

Malicious package

backpack-iosnpm

Advisory published Jun 24, 2026Updated Jun 24, 2026

backpack-ios is a confirmed malicious npm package (MAL-2026-6366) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in backpack-ios (npm)

MAL-2026-6366

Immediate action

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

npm uninstall backpack-ios

What this malware does

package.json declares "preinstall": "node index.js", causing index.js to execute automatically on npm install. The script collects host identifiers (os.hostname, os.userInfo, homedir, DNS servers, cwd, full package.json) and reads /etc/passwd and /etc/hosts via fs.readFileSync, then HTTPS POSTs the JSON payload to xopalguac3nk3bb10x9r4t6q7hdd13ps.oastify.com — a Burp Collaborator (OAST) subdomain used for out-of-band data exfiltration. The package name mirrors Skyscanner's Backpack iOS design-system package while shipping a ~2KB exfil-only payload with empty author/description fields, consistent with a dependency-confusion / typosquat lure. Installing this package directly leaks installer host identity and local user account data to an attacker-controlled endpoint.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

25f0d7ea98cef4ddcac8af3b854c37c1a8a3246a13357af60cb36589454657b5

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for backpack-ios (version 1.0.0).
If you installed it — respond
backpack-ios 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 backpack-ios was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. backpack-ios on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007413

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks backpack-ios-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