Which versions of kinvey-cli-wrapper are malicious?

The following npm versions of kinvey-cli-wrapper are flagged malicious: 0.3.1. Treat any of these as compromised.

How do I remediate kinvey-cli-wrapper if I installed it?

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

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

Yes — kinvey-cli-wrapper is associated with the GHSA-2mch-f3qc-jjgm 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 kinvey-cli-wrapper 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 kinvey-cli-wrapper (version 0.3.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kinvey-cli-wrapper across your stack and pipelines.

Malicious package

kinvey-cli-wrappernpm

Malicious code in kinvey-cli-wrapper (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191118

Immediate action

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

npm uninstall kinvey-cli-wrapper

What this malware does

The package kinvey-cli-wrapper was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.3.1

Indicators of compromise (SHA-256)

f5c927261aeaaa786117251a78d49a1dcc30a004d08df680b8f3b9ebf73be05e

c40e7aa2a954e976195783119a43a9b038a570885caee4bf84233bf196f03cfd

0cd908bc42e771527ecff3b0ef336122eb8d484f23f0402f511ca30dcb7b37dc

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

Campaign

GHSA-2mch-f3qc-jjgm

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks kinvey-cli-wrapper-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