@doaction/mapstorenpm
Malicious code in @doaction/mapstore (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
@doaction/[email protected] is published to the public npm registry under a sentinel-high version (99.99.99) with a pinned @doaction/shared: ^99.99.99 dependency — the canonical shape of a dependency-confusion attack designed to be resolved over a private internal @doaction/* package. package.json declares "preinstall": "node scripts/postinstall.js", which require()s @doaction/shared/bin/postinstall.js; a sibling preinstall.js wrapper similarly require()s @doaction/shared/bin/preinstall.js. The wrappers self-describe as 'Triggers safe environment telemetry on npm install' and the package's main src/index.js documents the purpose as collecting environment variables and sending them to Datadog. Both wrappers catch and silently swallow non-MODULE_NOT_FOUND errors so the install completes regardless of telemetry success/failure, minimizing installer visibility. The exfiltration runs unconditionally at npm install time with no user opt-in. Installer harm: CI/build environment variables (which routinely include cloud credentials, registry tokens, and CI secrets) are transmitted to a third-party endpoint whenever a build system mistakenly resolves this public package over the intended internal one.
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
Indicators of compromise (SHA-256)
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Scan your dependencies
O3 Security blocks malicious packages like this at install time and in CI.
Supply-chain protection