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

@wololasod/tiny-idnpm

@wololasod/tiny-id is a confirmed malicious npm package (MAL-2026-12331) that runs destructive / sabotage code (malicious versions 0.1.0, 0.1.1, 0.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @wololasod/tiny-id (npm)

MAL-2026-12331
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @wololasod/tiny-id

What this malware does

The package advertises itself as a tiny ID generator but its main entry dist/index.cjs contains an obfuscator.io + RC4 string-array VM that, on require/import, resolves a platform-specific configuration (win32/linux), downloads a remote executable over https to a temp/APPDATA path, and executes it via child_process.spawn (VBS launcher on Windows, direct spawn on Linux), then deletes the staged file. Staging filename observed: 'nupkg_system.diagnostics.performancecounter.8.0.0.py'. The loader additionally re-launches itself via spawn(process.execPath, [__filename], {detached:true, stdio:'ignore', windowsHide:true, env:{...process.env, RUN_PAYLOAD:...}}) and unrefs the child, producing a hidden, detached process that survives the parent. The loader includes obfuscator.io anti-analysis features: RC4-decoded string array, hex-named identifiers, eval.toString()/Function.prototype.bind.toString() '[native code]' integrity checks, and a djb2 caller-hash gate ('_$h!== 0x74F28336') that crashes if the code is reformatted. The same obfuscated dropper is also shipped in dist/index.d.ts, which is declared as the TypeScript types entry — a.d.ts file should contain pure type declarations, not executable code. None of this behavior relates to ID generation.

Malicious versions

3 flagged
0.1.00.1.10.1.3

Indicators of compromise (SHA-256)

4b86e785db5111f091312c26dc471a90839c0785a4989f25065555c82c64dd76
5b3ca8617b237bb3d8fd7d14aa18554118397e7b7faaea2e87cdd8433fef7a8f
84d9d02380d22d1874c6948d91ef38033e2f7ebfb233a89c1e1b3f4cc2bc6ef9

Detection & response playbook

Destructive / sabotage
  1. Find it

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

  2. If you installed it — respond

    @wololasod/tiny-id carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

  3. Did it already run?

    If @wololasod/tiny-id 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 @wololasod/tiny-id 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. @wololasod/tiny-id on npm has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014783IN-MAL-2026-014784IN-MAL-2026-014781

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @wololasod/tiny-id-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

@wololasod/tiny-id (npm) malicious package — MAL-2026-12331 | O3 Security