Which versions of commonweb-moneymovement are malicious?

The following npm versions of commonweb-moneymovement are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate commonweb-moneymovement if I installed it?

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

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

Yes — commonweb-moneymovement is associated with the IN-MAL-2026-013297, GHSA-j4gf-r356-ff9m 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 commonweb-moneymovement 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 commonweb-moneymovement (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging commonweb-moneymovement across your stack and pipelines.

Malicious package

commonweb-moneymovementnpm

commonweb-moneymovement is a confirmed malicious npm package (MAL-2026-10967) that steals credentials and exfiltrates sensitive data (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in commonweb-moneymovement (npm)

MAL-2026-10967

Immediate action

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

npm uninstall commonweb-moneymovement

What this malware does

Package [email protected] contains 2 files with no a static rule matches and no traced behavioral findings. The version number (99.9.1) and name pattern are consistent with an internal or placeholder package rather than a functional library, but no exfiltration, install-time code execution, credential handling, or network callback behavior is present in the shipped contents.

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.

The OpenSSF Package Analysis project identified 'commonweb-moneymovement' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

84f718c6b68fba15ac3506964439bc33c409cef1390f6cb22fa5a86d074e3a42

dee7c2ba53e2c7adae6a2b54776c21490794ee8f28fde98f5c61778380de1382

19b90b263929b0ea89e404dd7966680a5ed38d29cedf082e5f9da96ee624f8fb

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 commonweb-moneymovement (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging commonweb-moneymovement across your stack and pipelines.
If you installed it — respond
commonweb-moneymovement 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 commonweb-moneymovement 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 commonweb-moneymovement 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. commonweb-moneymovement on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-013297GHSA-j4gf-r356-ff9m

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks commonweb-moneymovement-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