Which versions of @revvity-signals/chemdraw-js are malicious?

The following npm versions of @revvity-signals/chemdraw-js are flagged malicious: 1.0.0, 1.0.3. Treat any of these as compromised.

How do I remediate @revvity-signals/chemdraw-js if I installed it?

Remove @revvity-signals/chemdraw-js 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 @revvity-signals/chemdraw-js — how do I know if it already compromised me?

If @revvity-signals/chemdraw-js 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.

Is @revvity-signals/chemdraw-js part of a known attack campaign?

Yes — @revvity-signals/chemdraw-js is associated with the GHSA-2vh3-gf8f-8524, RLMA-2025-06039, RLUA-2026-01049 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 @revvity-signals/chemdraw-js across my projects, lockfiles, and CI pipelines?

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

Malicious package

@revvity-signals/chemdraw-jsnpm

Malicious code in @revvity-signals/chemdraw-js (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192573

Immediate action

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

npm uninstall @revvity-signals/chemdraw-js

What this malware does

The package @revvity-signals/chemdraw-js 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

2 flagged

1.0.01.0.3

Indicators of compromise (SHA-256)

5a07504cb6db0747bda46340f3901e74b93fa28d2b12b5629eb19b6988ab3eaa

c53a6ff6ab4af77539873f6d418625d58f5d11a3fedda42efb25b91585218bbf

6b2e6a8e40a1983e76ccb694db2b6e8fb82ab35bba860bf71cfcc85f0b166022

667e390aa0b263b2b1aba0d4ad76706e236b9fc05b2645478faa8b829028f808

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @revvity-signals/chemdraw-js (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @revvity-signals/chemdraw-js across your stack and pipelines.
If you installed it — respond
Remove @revvity-signals/chemdraw-js 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 @revvity-signals/chemdraw-js 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.
How O3 protects you
O3 blocks @revvity-signals/chemdraw-js 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. @revvity-signals/chemdraw-js on npm has been identified as a malicious package (versions 1.0.0, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2vh3-gf8f-8524RLMA-2025-06039RLUA-2026-01049

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @revvity-signals/chemdraw-js-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