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

compass-e2e-testsnpm

Malicious code in compass-e2e-tests (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-922
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall compass-e2e-tests

What this malware does

The package compass-e2e-tests 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.

The OpenSSF Package Analysis project identified 'compass-e2e-tests' @ 99.0.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
99.0.0

Indicators of compromise (SHA-256)

9479d1900c70bc222c2561f8eee6d6e902b19fbcd609f8ee641c9036d46fac52
27a245065291bd7252411254769a1764aab8e228c8ca161708734a3d47d3c9ec
9a1c36b7819747a9ec6fee89af4a074c6feaef203a146bc554f20b1e795f8db1

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 compass-e2e-tests (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging compass-e2e-tests across your stack and pipelines.

  2. If you installed it — respond

    Remove compass-e2e-tests 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 compass-e2e-tests 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 compass-e2e-tests 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. compass-e2e-tests on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j29q-8q6j-p7rr

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks compass-e2e-tests-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.

compass-e2e-tests (npm) malicious package — MAL-2026-922 | O3 Security