Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@amplify-js/datastorenpm

Malicious code in @amplify-js/datastore (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2574
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @amplify-js/datastore

What this malware does

The package @amplify-js/datastore 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.0

Indicators of compromise (SHA-256)

7e339cf525d10d5783e176b0a833d0affac08e250b990f6fa8c0a44fdab33afc
efd7e80b9c74a9ab48a929d99c8daaabd6ed4dcbd05b9c59aa30730eec4c2e4c
a31c933f191cd94be3e10adb951ed57652fe41955589d37ce8c200c96256f36e

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @amplify-js/datastore (version 99.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @amplify-js/datastore across your stack and pipelines.

  2. If you installed it — respond

    Remove @amplify-js/datastore 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.

  3. Did it already run?

    If @amplify-js/datastore 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.

  4. How O3 protects you

    O3 blocks @amplify-js/datastore 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. @amplify-js/datastore on npm has been identified as a malicious package (version 99.9.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cqpc-xhmp-qr76RLMA-2026-01847

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @amplify-js/datastore-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.

@amplify-js/datastore (npm) malicious package — MAL-2026-2574 | O3 Security