Which versions of mobicwkgjmx are malicious?

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

How do I remediate mobicwkgjmx if I installed it?

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

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

Yes — mobicwkgjmx is associated with the GHSA-5qfm-5r6q-m38q, IN-MAL-2026-017516 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 mobicwkgjmx 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 mobicwkgjmx (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 mobicwkgjmx across your stack and pipelines.

Malicious package

mobicwkgjmxnpm

mobicwkgjmx is a confirmed malicious npm package (MAL-2026-13827) 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 mobicwkgjmx (npm)

MAL-2026-13827

Immediate action

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

npm uninstall mobicwkgjmx

What this malware does

Package [email protected] contains only two scanned files and no static or traced findings indicating credential access, install-time execution of external code, silent-relay, dropper, backdoor, or self-propagation. The random-looking package name is unusual but is not by itself a supply-chain threat, and no code behavior in this version demonstrates harm to an installer.

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)

68a802febb40fa459d8bc59af7afed267f6c8c4982679f00584e4110af3125ba

790620aeb9129471875ad3bbfd9e5c379b4cf2a8a5cbc920148be5d37ca3f9d1

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 mobicwkgjmx (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 mobicwkgjmx across your stack and pipelines.
If you installed it — respond
mobicwkgjmx 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 mobicwkgjmx 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 mobicwkgjmx 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. mobicwkgjmx 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-5qfm-5r6q-m38qIN-MAL-2026-017516

References

Credits

Amazon Inspector · finder

Detect & block this

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