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

ing-web-v5npm

ing-web-v5 is a confirmed malicious npm package (MAL-2026-2822) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ing-web-v5 (npm)

MAL-2026-2822
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ing-web-v5

What this malware does

The package ing-web-v5 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 'ing-web-v5' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

6d0082d12c6909a9fcab28a2f2ad51cabf24e383f813999f6ad399ffcce08690
f32dd0f0eff32e970526305378a6623e9af62ab133ddcf04a21aa92f1eb95f26
9e7004b49a2628c8e4ae0eb894bf23d52b8c6bef3911ea2ce955dda180f237d8

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

  2. If you installed it — respond

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

Campaign

GHSA-5c9h-x827-2v9f

References

Credits

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

Detect & block this

O3 blocks ing-web-v5-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

ing-web-v5 (npm) malicious package — MAL-2026-2822 | O3 Security