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

downlynpmnpm

downlynpm is a confirmed malicious npm package (MAL-2026-5666) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in downlynpm (npm)

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

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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

3 flagged
1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

c54f0f73fe269f9054d27204762149882fd85c82c575dfa40738014f7a594090
0a04b70a8d532cead70309fd97fc63afc3e1e3a411443076da4d90d2cb4b9bc5
c660fc13390aa049eb64c8baa8789e82ede03d86dfc40436bac047dcd61b931c
e24cff1ce01f7f12ffa1c45d01ffed834ff22ce63a2f218b2f0f2c5abcac2d8c

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

  2. If you installed it — respond

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

Campaign

GHSA-vq59-5vfc-9rh5IN-MAL-2026-008914IN-MAL-2026-008920IN-MAL-2026-008922

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks downlynpm-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

downlynpm (npm) malicious package — MAL-2026-5666 | O3 Security