Which versions of mobicommn are malicious?

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

How do I remediate mobicommn if I installed it?

mobicommn is a typosquat — you almost certainly intended a legitimately-named package. Remove mobicommn, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed mobicommn — how do I know if it already compromised me?

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

Yes — mobicommn is associated with the GHSA-gpmq-h9wr-wm89, IN-MAL-2026-017483 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 mobicommn 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 mobicommn (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mobicommn across your stack and pipelines.

Malicious package

mobicommnnpm

mobicommn is a confirmed malicious npm package (MAL-2026-13826) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mobicommn (npm)

MAL-2026-13826

Immediate action

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

npm uninstall mobicommn

What this malware does

The tarball contains just index.html and package.json (main: index.html). index.html mimics a Cloudflare Turnstile challenge and, on the Turnstile callback, reconstructs a destination URL from a rotated obfuscated string array and calls window.location.replace to redirect. There are no preinstall/install/postinstall/prepare scripts, and Node does not execute HTML on require, so the redirect does not fire on npm install or on import of the package. The shipped artifact is only reachable if the HTML file is loaded in a browser, which is not a normal consumer path for an npm dependency.

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

1.0.0

Indicators of compromise (SHA-256)

78d25e60a5b3158086ec2c0aa7af9188a871ca73ebf0a917d7bc5f15050f7942

b1fdfcbe5e1e182dcc1972748c2ccb13792e2db392a5404ba08a423b8d184da5

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mobicommn (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mobicommn across your stack and pipelines.
If you installed it — respond
mobicommn is a typosquat — you almost certainly intended a legitimately-named package. Remove mobicommn, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If mobicommn 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 mobicommn 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. mobicommn 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

GHSA-gpmq-h9wr-wm89IN-MAL-2026-017483

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mobicommn-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