Which versions of @bookiply/core are malicious?

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

How do I remediate @bookiply/core if I installed it?

Remove @bookiply/core 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 @bookiply/core — how do I know if it already compromised me?

If @bookiply/core 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 @bookiply/core part of a known attack campaign?

Yes — @bookiply/core is associated with the GHSA-8mf9-v5mc-4ch3, RLMA-2026-04692 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 @bookiply/core across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @bookiply/core (version 99.9.1).

Malicious package

@bookiply/corenpm

Advisory published Apr 13, 2026Updated Jul 9, 2026

@bookiply/core is a confirmed malicious npm package (MAL-2026-2579) 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 @bookiply/core (npm)

MAL-2026-2579

Immediate action

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

npm uninstall @bookiply/core

What this malware does

The package @bookiply/core 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.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

2887f360cb9e14cb6c6065ddc86c7aa69674edb8d09486f31b3256f376894e8f

dd6b31f3177ed87f264b6338a9fe54bb910142b5622bba68372acbac801268d2

935af86c335822ee2967f33730ad1d0e617831ad8af25711dd969139e0e69bfd

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @bookiply/core (version 99.9.1).
If you installed it — respond
Remove @bookiply/core 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 @bookiply/core 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. @bookiply/core 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-8mf9-v5mc-4ch3RLMA-2026-04692

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @bookiply/core-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