NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@mobile-platform/magnetic-componentsnpm

Advisory published Updated

@mobile-platform/magnetic-components is a confirmed malicious npm package (MAL-2026-18448) that executes malicious code on install (malicious versions 0.0.1, 0.0.2, 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @mobile-platform/magnetic-components (npm)

MAL-2026-18448
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @mobile-platform/magnetic-components

What this malware does

@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.

Malicious versions

3 flagged
0.0.10.0.20.0.3

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for @mobile-platform/magnetic-components (3 malicious versions).

  2. If you installed it — respond

    Remove @mobile-platform/magnetic-components from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @mobile-platform/magnetic-components 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. @mobile-platform/magnetic-components on npm has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • InvisiRisk, Inc. · finder

Detect & block this

O3 blocks @mobile-platform/magnetic-components-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@mobile-platform/magnetic-components (npm) malicious package — MAL-2026-18448 | O3 Security