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

demo-awesome-date-parser-testnpm

demo-awesome-date-parser-test is a confirmed malicious npm package (MAL-2026-11099) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.2, 0.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in demo-awesome-date-parser-test (npm)

MAL-2026-11099
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall demo-awesome-date-parser-test

What this malware does

The package advertises itself as a date parser but ships a heavily obfuscated payload in src/index.js. The exported demoParseDate function invokes injectScriptIfNeeded, which registers a jQuery form-submission handler that reads submitted form field values, stores them in localStorage under keys 'sendToUnload_secretData' and 'sendToUnload_secretDataBase64', and POSTs them via fetch to a URL built from location.host with the path '/leak?data_stolen_on_unload_base64='. A window unload handler additionally exfiltrates the buffered values twice via navigator.sendBeacon to the same '/leak?...' path. injectScriptIfNeeded also loads remote JavaScript by evaluating a dynamic import of '<host>/tag_added_via_script_import.js' and by appending a <script src='//<host>/tag_added_via_script_file_tag_appending.js'> tag to the document, giving the author arbitrary in-page code execution. The module also assembles code at runtime via eval, new Function, and setInterval(setTimeout,...) on strings drawn from an obfuscated string array, and manipulates the end-user clipboard through navigator.clipboard.writeText/readText and a hidden-textarea document.execCommand('copy') that writes a literal 'malware test text copy' string. Author-written literals in the bundle ('Attack vector: eval execution', 'stolen-data-sended-on-unload-event-base64', 'Code executed on event state via window.onload') confirm intent. The package name 'demo-awesome-date-parser-test' and version 0.0.7 are consistent with a demonstration/test artifact, but the code performs real exfiltration and remote-script-loading behavior against any consumer that loads it.

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

7 flagged
0.0.10.0.20.0.30.0.40.0.50.0.60.0.7

Indicators of compromise (SHA-256)

6e554422e7b097902e753eb63c772c66845f3f19bf0c2974f6fbeb9fe441ec34
78f9d8522a52a8a7b511febd77ca55d74649d44804ca0da0dc4832646adb632d
c46165721d6b575d475d3af67d3de1320285aa30f802144c08bd7bc574e2f06b
3dac7edbd7a941a69901501e2f602b37a483dde93aac9af9270f146fea0e7992
e5cccf4c1379e6c3f9af7dde45277b1c4db552a0ad878bc08378ad6e8879b497
291bd1d754bffc6d57f45f76cbdd6abb09da6cd53d84982a99b8eb6689dd5794
a9192adc99bd98d23c6c4c8cc43dd10047a3d4b99f1d236b2937b0fd121830b9
4e126cd9ddc6434c9a1ffad2d290c78c1c46b92db48916fca78458f7a276e06d

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 demo-awesome-date-parser-test (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging demo-awesome-date-parser-test across your stack and pipelines.

  2. If you installed it — respond

    demo-awesome-date-parser-test 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 demo-awesome-date-parser-test 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 demo-awesome-date-parser-test 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. demo-awesome-date-parser-test on npm has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xcf3-mw56-cqm5IN-MAL-2026-010904IN-MAL-2026-010897IN-MAL-2026-010899IN-MAL-2026-011071IN-MAL-2026-011119IN-MAL-2026-011185IN-MAL-2026-013345

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks demo-awesome-date-parser-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

demo-awesome-date-parser-test (npm) malicious package — MAL-2026-11099 | O3 Security