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

cos-js-sdk-v6npm

Malicious code in cos-js-sdk-v6 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192557
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cos-js-sdk-v6

What this malware does

The package cos-js-sdk-v6 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
999.0.0

Indicators of compromise (SHA-256)

8c001845c7ca3a227b7e24858fde28811305d6f37bbf10d84f0fa5276c1d146c
16d4e667425231cedc1d2417e80767126bd48fa3afc7cc2bbb14ef6ae45df684
6e668c29d209a91467b38e88589f591a0b56585bad9bd72fa995442796959f9a
fab02a7712177bb4ebfbac6b3bfe6b080b118b4151bc59422cda67d72d8c5a1d

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

  2. If you installed it — respond

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

Campaign

GHSA-r77x-55q8-xq2vRLMA-2025-06104RLUA-2026-01228

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks cos-js-sdk-v6-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
cos-js-sdk-v6 (npm) malicious package — MAL-2025-192557 | O3 Security