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

@thone33/core-utilsnpm

@thone33/core-utils is a confirmed malicious npm package (MAL-2026-6564) 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 @thone33/core-utils (npm)

MAL-2026-6564
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @thone33/core-utils

What this malware does

@thone33/core-utils 1.0.4 is a loader stub. Its main entry (index.js) imports activate from the same-author dependency @thone33/analytics-injector and invokes it at module top level whenever process.env.NODE_ENV === 'production'. The author's own inline comment describes this as silently activating a payload in production ('ATIVA O PAYLOAD SILENCIOSAMENTE (em produção)'). The package is advertised as 'Core utilities', which does not justify production-gated invocation of an 'analytics-injector' dependency. The NODE_ENV=production gate is a developer-laptop-dormant / production-fires evasion pattern: consumers' local dev and CI environments see nothing, while deployed production processes execute whatever code the author publishes under @thone33/analytics-injector. Because the injector is in the same author scope and pinned as ^1.0.0, the author can ship arbitrary additional code into consumers' production runtimes via a minor/patch release without any change to this package.

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

6 flagged
1.0.01.0.11.0.21.0.31.0.41.0.5

Indicators of compromise (SHA-256)

05561d1a31165dab72c5090437ccfa7a85035a2b4fdf6a646eca59b62dd87120
bc21b99e8aa825cc496faec3251ba814d5fdec8a7fe6294407a9b067e0558b2c
cfc57cb70348ed66a74b958d3155234acebe740fd4d72e8c5f4e1fd939ea8ec7
0bc45a824950b13adc9f82ee769e0025f4c353cf74a1ddd62e7b9626a8e5ca68
2e89994f9f3c8da051834049643a2a04df8b6fa9c14452fafceb6080e9f85be9
80421aa7cecd55d71cbde625bbb0dd5febc8aef00f32a1a6e1b8601b1c8d2673
734ac2e7b7bf060338154bbcca4efa5f64fddd9a6f3832d5127751ba37be9edb

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

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-007731IN-MAL-2026-007734IN-MAL-2026-007733IN-MAL-2026-007732IN-MAL-2026-007729IN-MAL-2026-007730GHSA-w2wf-8vp4-86mq

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @thone33/core-utils-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

@thone33/core-utils (npm) malicious package — MAL-2026-6564 | O3 Security