NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

laserlogsinknpm

Advisory published Updated

laserlogsink is a confirmed malicious npm package (MAL-2026-2001) that executes malicious code on install (malicious versions 2.1.0, 9000.0.0, 9000.0.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in laserlogsink (npm)

MAL-2026-2001
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall laserlogsink

What this malware does

The package laserlogsink 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 'laserlogsink' @ 9000.0.1 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

4 flagged
2.1.09000.0.09000.0.19000.0.2

Indicators of compromise (SHA-256)

71e951199a264d12fa81442f96062d99c5c37ffaf64b5c71b47783846b6014df
3028499625bf1c6a218f2332e6cecfd2af12b14859ce0411350e5ae84670a067
a395b7649d8ffc5bba2148c036a508ef75bf9fbe006f601be97f10cb6d062b14
474d1b0019630f528f0f4bbed72d636f649257ffca929db3211799fe870a13cb

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for laserlogsink (4 malicious versions).

  2. If you installed it — respond

    Remove laserlogsink 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 laserlogsink 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. laserlogsink on npm has been identified as a malicious package (versions 2.1.0, 9000.0.0, 9000.0.1, 9000.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g52g-7jj2-8phv

References

Credits

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

Detect & block this

O3 blocks laserlogsink-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.

Explore

laserlogsink (npm) malicious package — MAL-2026-2001 | O3 Security