@mobile-platform/magnetic-components (npm) · Malicious Code
Affects @mobile-platform/magnetic-componentsSource GCVE Database
Malicious package : remove @mobile-platform/magnetic-components and rotate any secrets on hosts that installed it.
Data as of 11 Nov 2026, 00:22 UTC
Malicious package
Published to npm · OSV MAL-2026-18448
What to do
Remove @mobile-platform/magnetic-components from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@mobile-platform/magnetic-components | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
@mobile-platform/magnetic-components is a dependency-confusion package: its description says the scoped name is referenced in the Meraki Dashboard Android app's bundled JavaScript and was unclaimed on the public registry, so a build that resolves `@mobile-platform` from npm runs its code instead of the intended private package. Its preinstall script runs `node preinstall.js` on npm install; in 0.0.1 and 0.0.2 it writes `DEPENDENCY_CONFUSION_POC_MARKER.txt` into the working directory, and in 0.0.3 it makes a DNS lookup of a fixed subdomain of `dbhmeq71af5395un3p70tujr84cuwuyg7.oast.me`, an interactsh callback host, signalling that the package was installed. It sends no host data beyond the lookup itself, but unreviewed code from an outside publisher has run with the installing user's privileges. The npm account io-8 published the three versions on 2026-10-29. --- _-= Per source details. Do not edit below this line.=-_ ## Source: ghsa-malware (9594fe5dcfe6dbe11568cb09f324f04b3050c8e19ef0a0523d63e0ba88d16ff9) 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.