Which versions of @grappi/automations are malicious?

The following npm versions of @grappi/automations are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate @grappi/automations if I installed it?

Remove @grappi/automations from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @grappi/automations — how do I know if it already compromised me?

If @grappi/automations was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @grappi/automations part of a known attack campaign?

Yes — @grappi/automations is associated with the GHSA-85ph-rvjg-3hmr, RLMA-2026-04729, RLUA-2026-05429 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 @grappi/automations across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @grappi/automations (version 99.9.1).

Malicious package

@grappi/automationsnpm

Advisory published Jun 29, 2026Updated Jul 23, 2026

@grappi/automations is a confirmed malicious npm package (MAL-2026-6625) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @grappi/automations (npm)

MAL-2026-6625

Immediate action

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

npm uninstall @grappi/automations

What this malware does

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

99.9.1

Indicators of compromise (SHA-256)

dfa70084df92420d9b31f4eb1da3b47bccc78cc677a9f6fb3ac242c857f2e925

b24b7c125e3612783697481227d6353af17c2a0cf5c4b551d78d9f3dd55b96b3

d3065b88cbb35d4fc93b7f836f8991a7548d3cac3c0a1df7c681e0036359f5b0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @grappi/automations (version 99.9.1).
If you installed it — respond
Remove @grappi/automations from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @grappi/automations was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @grappi/automations 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

GHSA-85ph-rvjg-3hmrRLMA-2026-04729RLUA-2026-05429

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @grappi/automations-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