Which versions of babel-preset-kinvey-flex-service are malicious?

The following npm versions of babel-preset-kinvey-flex-service are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate babel-preset-kinvey-flex-service if I installed it?

babel-preset-kinvey-flex-service 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 babel-preset-kinvey-flex-service — how do I know if it already compromised me?

If babel-preset-kinvey-flex-service 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 babel-preset-kinvey-flex-service part of a known attack campaign?

Yes — babel-preset-kinvey-flex-service is associated with the GHSA-c8pf-4gvg-m3qj 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 babel-preset-kinvey-flex-service 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 babel-preset-kinvey-flex-service (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging babel-preset-kinvey-flex-service across your stack and pipelines.

Malicious package

babel-preset-kinvey-flex-servicenpm

Malicious code in babel-preset-kinvey-flex-service (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191069

Immediate action

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

npm uninstall babel-preset-kinvey-flex-service

What this malware does

The package babel-preset-kinvey-flex-service 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.1.1

Indicators of compromise (SHA-256)

687c3986ebb58be81ff2cffbf4beaf3303f9396beecacbf8eaab8983cb350954

73a0e431e7dec9aa734048ca70ad424140f4ccb7ccd17d79b03bd6c55e2d7390

95227fb68cd76580469df042e11e087ac694eaf2d50c6ac95514edcaee6056a4

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

Campaign

GHSA-c8pf-4gvg-m3qj

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks babel-preset-kinvey-flex-service-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