More stories

  • in

    Singapore moots mandatory offsite verification for financial institutions

    Singapore is considering the need for various personal information, such as password and biometrics, to facilitate “non-face-to-face” verification for financial services. This comes amidst a rise in impersonation scam cases and risks of personal data theft. 
    In a consultation paper released Tuesday, the Monetary Authority of Singapore (MAS) mooted the mandatory use of at least one of a several types of information to verify individuals tapping an offsite financial service channel, such as phone or online banking, before processing any transaction or request. 
    These include information only the individual knows such as password or PIN, or only the individual has such as one-time password generated by a hardware token issued to the individual or software token activated on the individual’s mobile device. Information used for verification also can include the individual’s biometric data such as face or fingerprint recognition or information that is known only between the individual and the financial institution such as account transaction information. 

    Global pandemic opening up can of security worms
    Caught by the sudden onslaught of COVID-19, most businesses lacked or had inadequate security systems in place to support remote work and now have to deal with a new reality that includes a much wider attack surface and less secured user devices.
    Read More

    MAS also proposed that financial institutions be barred from using commonly used personal information such as NRIC number, residential address, and date of birth as the only means of identity verification. 
    Such requirements were necessary amidst the increasing impersonation scam cases and to address growing risks from theft and misuse of personal data. 
    MAS’ chief cybersecurity officer Tan Yeow Seng said: “Personal information such as NRIC number and date of birth are often provided by members of public for various purposes, such as filling in an application form. This information, if fallen into the wrong hands, can be used for impersonation fraud. 
    “Financial institutions already have in place these identity verification practices. The proposed Notice [outlined in the consultation paper] will further bolster consumer confidence in financial institutions by making these identity verification practices compulsory during non-face-to-face financial transactions,” Tan said. “Consumers should also play their part by not disclosing their online banking login credentials such as account username, PIN number, and one-time password.”

    The industry regulator said it was seeking feedback on the proposed requirements, which should be submitted before December 9. 
    In a separate statement Tuesday, MAS also urged the need for financial institutions to review their security controls as remote work and other safe management measures, implemented due to the COVID-19 pandemic, could give way to added technology-related risks.
    It recommended a list of added controls these organisations should consider adopting, such as reviewing whether their current risk profiles had changed and remained acceptable and if they had adequate risk mitigating measures. They also should step up oversight of third-party vendors and their controls, monitoring and securing remote access by third-parties to their systems. 
    In addition, MAS recommended that financial institutions strengthened the governance of the use of open source software, which vulnerabilities typically were targeted and exploited by threat actors. These organisations should establish policies and procedures on the use of open source software and ensure software codes were reviewed and tested before deployment.
    MAS’ managing director Ravi Menon said: “As the [pandemic] prolongs, [financial institutions’] resilience will come under greater stress as cyber attackers look for new vulnerabilities. Financial institutions must remain alert and nimble and strengthen their defences against emerging cyber threats.”
    The industry regulator in August last year implemented new legislation aimed at enhancing the cybersecurity posture of financial organisations, outlining mandatory requirements with which these businesses would have to comply by August 2020. The Notice on Cyber Hygiene outlined steps these businesses must take to mitigate the growing risk of cyber threats, including complying with six main requirements such as implementing robust security for IT systems, ensuring updates were applied “in a timely manner” to address system security flaws, and deploying security devices to restrict unauthorised network traffic. 
    it also would be mandatory for these companies to implement measures to mitigate risks of malware infection, secure the use of system accounts that have special privileges, and beef up user authentication for critical systems, including systems used to access customer data. 
    RELATED COVERAGE More

  • in

    Chrome to block tab-nabbing attacks

    Image: Google // Composition: ZDNet
    Google will deploy a new security feature in Chrome next year to prevent tab-nabbing, a type of web attack that allows newly opened tabs to hijack the original tab from where they were opened.
    The new feature is scheduled to go live with Chrome 88, to be released in January 2021.
    While the term “tab-nabbing” refers to a broad class of tab hijacking attacks [see OWASP, Wikipedia], Google is addressing a particular scenario.
    This scenario refers to situations when users click on a link, and the link opens in a new tab (via the “target=_blank” attribute).
    These new tabs have access to the original page that opened the new link. Via the JavaScript “window.opener” function, the newly opened tabs can modify the original page and redirect users to malicious sites.

    Image: OWASP
    This type of attack has powered quite a few phishing campaigns across the years. To mitigate this threat, browser makers like Apple, Google, and Mozilla have created the rel=”noopener” attribute.
    For the past few years, security researchers and top web developers have constantly advocated that website owners add the rel=”noopener” to all the links where they also used the “target=_blank” attribute as a way to block tab-nabbing attacks [1, 2].

    However, most of today’s websites end up abandoned, or website owners don’t have the time to keep up with the latest trends in web development and web security.
    That is why, in 2018, both Apple and Mozilla moved to incorporate the rel=”noopener” attribute and automatically add it to all newly opened tabs inside Safari and Firefox by default.
    With Chrome 88, Google will be catching up with the two other major browser makers. Besides adding this feature in Chrome, the new tab-nabbing protection will also go be added to all the other Chromium-based browsers, such as Edge, Opera, Vivaldi, and Brave. More

  • in

    New 'Ghimob' malware can spy on 153 Android mobile applications

    Security researchers have discovered a new Android banking trojan that can spy and steal data from 153 Android applications.

    Named Ghimob, the trojan is believed to have been developed by the same group behind the Astaroth (Guildma) Windows malware, according to a report published on Monday by security firm Kaspersky.
    Kaspersky says the new Android trojan has been offered for download packed inside malicious Android apps on sites and servers previously used by the Astaroth (Guildama) operation.
    Distribution was never carried out via the official Play Store.
    Instead, the Ghimob group used emails or malicious sites to redirect users to websites promoting Android apps.
    These apps mimicked official apps and brands, with names such as Google Defender, Google Docs, WhatsApp Updater, or Flash Update. If users were careless enough to install the apps despite all the warnings shown on their devices, the malicious apps would request access to the Accessibility service as a final step in the infection process.
    If this was granted, the apps would search the infected phone for a list of 153 apps for which it would show fake login pages in an attempt to steal the user’s credentials.

    Most of the targeted apps were for Brazilian banks, but in recently updated versions, Kaspersky said Ghimob also expanded its capabilities to start targeting banks in Germany (five apps), Portugal (three apps), Peru (two apps), Paraguay (two apps), Angola and Mozambique (one app per country).
    Furthermore, Ghimob also added an update to target cryptocurrency exchange apps in attempts to gain access to cryptocurrency accounts, with Ghimob following a general trend in the Android malware scene that has slowly shifted to target cryptocurrency owners.
    After any phishing attempt was successful, all collected credentials were sent back to the Ghimob gang, which would then access a victim’s account and initiate illegal transactions.
    If accounts were protected by hardened security measures, the Ghimob gang used its full control over the device (via the Accessibility service) to respond to any security probes and prompts shown on the attacked smartphone.
    Ghimob’s features aren’t unique, but actually copy the make-up of other Android banking trojans, such as BlackRock or Alien.
    Kaspersky noted that Ghimob’s development currently echoes a global trend in the Brazilian malware market, with the very active local malware gangs slowly expanding to target victims in countries abroad. More

  • in

    Tasmania makes big leaps in Cisco Australian Digital Readiness Index

    Tasmania has risen to first place in Australia in terms of ease to do business in the Cisco Australian Digital Readiness Index 2020 report, and when combined with its lack of coal use and reliance on hydro, the state jumped from near the bottom of the Australian states ranking to be firmly mid-table.
    The Apple Isle gained its increase on the back of having the highest five-year business survival rate in the country, being rated as the state with the highest level of government support for small businesses and having the second-highest rate of confidence among small to medium-sized businesses. The state was also boosted for having 99.9% of its premises able to receive an NBN connection.
    On the flip side, Tasmania had the second-lowest per capita level of business investment in research and development.
    Overall, the postage stamp-sized ACT was rated the most digitally ready place in Australia, followed by New South Wales, Western Australia, Tasmania, Queensland, South Australia, and the Northern Territory.
    As the home of the Commonwealth public service, the sheep paddock cum national capital scored well for having a trained labour force, high government expenditure per capita on R&D, and being able to cater for basic needs. It dropped down the ranking, however, in categories such as startup environment and ease of doing business.
    Leading the way in venture capital investment was NSW, which had almost double that of the now second-placed ACT. Despite this, the state was ranked only sixth for technology adoption and seventh for technology infrastructure.
    The report, which was based on surveys completed in June 2020, was an update on a report first completed in 2018.

    Vice president of Cisco ANZ Ken Boal said the first report was a chance to encourage businesses and governments to increase digital investments.
    “Two years later the value of those investments have been repaid many times over and has provided Australia with a robust and comprehensive digital capability that has been essential for navigating through the COVID-19 crisis and building economic recovery post-pandemic,” he said.
    “However, it is important that we don’t become complacent with Australia’s digital readiness. This report highlights the need for accelerating new investment to improve Australia’s global competitiveness to keep up with competitor nations and bridge the divide between states and territories to build societal resilience.
    “Digitally advanced countries such as Singapore, which ranked first in the global index this year, should help Australia to set the ambition for its digital readiness.”
    Earlier in the week, the Australian government released submissions to its proposed Security Legislation Amendment (Critical Infrastructure) Bill 2020, which would expand the obligations in the Security of Critical Infrastructure Act 2018 to the communications, financial services and markets, data storage and processing, defence industry, higher education and research, energy, food and grocery, healthcare and medical, space technology, transport, and water and sewerage sectors.
    The tech giants, including Cisco, asked that definitions and classifications be clarified, particularly around terms such as data and cloud computing.
    “We, and I think we weren’t the only ones, we made a comment about whether data centres should be an industry in itself — because obviously every business that could be caught by the [Bill] is probably operating a data centre or has data in a data centre or relies on a data centre to access its critical applications,” Cisco ANZ director of government affairs Tim Fawcett told journalists on Tuesday.
    “So we made the point that that shouldn’t necessarily be an industry in and of itself.”
    Late last month, Cisco announced an update to its SecureX set of products that involved the company pointing out for the first time in 13 years it had reduced the number of product names on its security portfolio by half.
    “I think we at Cisco have done a lot of things right over the years and then there’s a few things … that we could probably do better,” Cisco senior vice president and general manager for security Jeetu Patel told ZDNet.
    “We found in security that our products were getting to be so convoluted to understand on what they did and what they were that there were just far too many things, and for a new person coming in, it just would make your head hurt.”
    Patel added that Cisco has bundled products together in a more logical way and given products names that are descriptive.
    “So that people don’t have to say ‘Well what is that?’ and let’s make sure that we do without acronyms, and just talk about names that are very descriptive,” he said.
    Related Coverage More

  • in

    Former Microsoft engineer sentenced to nine years in prison for stealing $10 million

    A former Microsoft software engineer that was convicted for stealing more than $10 million from the company has been sentenced to nine years in prison.
    The judgment, made by a jury, found that the charged individual, Volodymyr Kvashuk, committed 18 felonies. This consisted of five counts of wire fraud, six counts of money laundering, two counts of aggravated identity theft, two counts of filing false tax returns, and one count each of mail fraud, access device fraud, and access to a protected computer in furtherance of fraud.
    Kvashuk worked as a Microsoft contractor before becoming an employee in August 2016. He was then fired in June 2018 after the company discovered his actions of theft. 
    According to records filed in the case and testimony at trial, during Kvashuk’s time at Microsoft, he used his testing privileges to steal “currency stored value” such as digital gift cards. He then resold these goods on the internet, using the proceeds to purchase a $1.6 million dollar lakefront home and a $160,000 Tesla vehicle, the Department of Justice said.
    When making these thefts, Kvashuk used three test email accounts associated with other employees in an attempt to mask any digital evidence that traced the thefts to him. These accounts, combined, purchased roughly $10.1 million worth of currency stored value.
    “Stealing from your employer is bad enough, but stealing and making it appear that your colleagues are to blame widens the damage beyond dollars and cents,” US Attorney Brian Moran said.  
    “This case required sophisticated, technological skills to investigate and prosecute, and I am pleased that our law enforcement partners and the US Attorney’s Office have the skill sets needed to bring such offenders to justice.”

    He also used a bitcoin “mixing” service in an attempt to hide the source of the funds that passed into his bank and investment accounts. Across a seven-month span, approximately $2.8 million in bitcoin was transferred to his bank and investment accounts. These amounts were then filed as gifts from a relative in his tax returns.
    “Kvashuk’s scheme involved lies and deception at every step. He put his colleagues in the line of fire by using their test accounts to steal [currency stored value]. Rather than taking responsibility, he testified and told a series of outrageous lies. There is no sign that Kvashuk feels any remorse or regret for his crimes,” prosecutors wrote to the court.
    Along with the prison sentence, Kvashuk has also been ordered to pay $8.3 million in restitution and may be deported to Ukraine following his prison term.
    Related coverage
    Four former eBay employees set to plead guilty to cyberstalking charges in US
    Two other eBay employees are currently labelled as co-conspirators, but they have not been charged.
    Chinese national receives 18-month sentence for stealing US semiconductor trade secrets
    He was one of six individuals that were indicted, with the remaining five currently labelled as fugitives by the US government.
    US provides new expanded set of espionage charges against former Twitter employees
    The charges have expanded from two to seven.
    DoJ charges four brothers for defrauding Amazon in overshipping scheme
    In one instance, the brothers allegedly sent 7,000 toothbrushes to Amazon despite the e-commerce giant requesting for one case of disinfectant spray.
    Scientist sentenced to 2 years behind bars for stealing next-generation battery tech secrets
    The intellectual property had an estimated value of $1 billion to the US company it belonged to. More

  • in

    Tech giants not convinced Australia's critical infrastructure Bill is currently fit for purpose

    The tech sector has taken issue with a handful of proposals made by the federal government in its Security Legislation Amendment (Critical Infrastructure) Bill 2020, specifically around government step-in powers and a potential misunderstanding of the relationship between cloud service providers (CSPs) and their customers.
    The amendments in the Bill are aimed at enhancing the obligations in the Security of Critical Infrastructure Act 2018, and expanding its coverage to the communications, financial services and markets, data storage and processing, defence industry, higher education and research, energy, food and grocery, healthcare and medical, space technology, transport, and water and sewerage sectors.
    The Bill, if passed, would introduce a positive security obligation (PSO) for critical infrastructure entities, supported by sector-specific requirements and mandatory reporting requirements; enhanced cybersecurity obligations for those entities most important to the nation; and government assistance to entities in response to significant cyber attacks on Australian systems.
    Read more: Australia’s critical infrastructure definition to span communications, data storage, space  
    Commenting on the proposed Bill, Microsoft asked that in crafting such requirements for CSPs, the legislation should recognise the customer relationships that these organisations have with critical infrastructure operators “who have already imposed significant compliance requirements to meet existing regulatory obligations”.
    Its submission [PDF] on the Bill has asked the government to separate data centres and CSPs in the sectoral definitions; align Australian regulatory requirements with international standards; map existing regulatory requirements and security obligations met by CSPs and “harmonise those requirements to avoid duplication”; create protocols that ensure that the operator of the critical infrastructure systems is the focal point for any of the proposed obligations; and create clearly identifiable thresholds and checks for the use of the ministerial direction powers.
    Salesforce, meanwhile, has recommended that sectoral definitions be narrowed and clarified — particularly as it pertains to “data and the cloud”.

    “Salesforce encourages an approach which concentrates on regulated entities which control the systems of national significance, not service providers or processors that work across sectors,” it wrote in its submission [PDF].
    “Whilst Salesforce welcomes risk-based elements of the proposed framework, we recommend that Australia not pursue compliance-oriented mechanisms.”
    The CRM giant recommended concentrating oversight and expertise in a single agency and taking into account existing practices within each vertical.
    It also recommended that data and/or system security rules should consider classification, criticality, and sensitivity of the asset being protected.
    Offering its support for something similar, Cisco in its submission [PDF] said regulators and industry bodies informing classification of entities under the framework should include clear lines of accountability.
    This Bill also introduces a government assistance regime to respond to serious cybersecurity incidents that applies to all critical infrastructure sector assets.
    “Government recognises that industry should and in most cases, will respond to the vast majority of cybersecurity incidents, with the support of government where necessary,” the Bill’s explanatory document stated. “However, government maintains ultimate responsibility for protecting Australia’s national interests. As a last resort, the Bill provides for government assistance to protect assets during or following a significant cyber attack.”
    While Microsoft said it acknowledged that there may be emergency scenarios where the government may consider the need for direct action with critical infrastructure operators, it believes such actions must only occur as a last resort and “under a framework that incorporates robust checks and balances, as well as the Commonwealth Ombudsman acting on behalf of the private sector that reflects the interests and risks of undertaking such an action”.
    “The use of such powers should be subject to a significant threshold, time limited and require independent authorisation,” it wrote.
    “In the rare instances where ministerial direction is warranted, we recommend that it be narrowed to apply to circumstances in which gaps in abilities to defend and repel cyberthreat activity have been demonstrated during joint preparedness exercises among the government and private sector.”
    Similarly, Salesforce said extraordinary circumstances that would require emergency government powers should be carefully defined to “establish full clarity and mutual expectations of the standards, liability, and procedures that apply”.
    “Any decision should have the ability for judicial redress,” it added.
    Cisco requested there be checks and balances for all government assistance, especially for step-in powers.
    “Without a defined operating model on how the step in process would work, it is difficult to determine the checks and balances required but there are examples provided in other parliamentary reviews into security laws that could provide guidance,” it wrote.
    “It is not clear yet what impact the government assistance powers to step-in could have on the operation of companies that are either not headquartered in Australia or operate in offshore markets.”
    Amazon Web Services (AWS) also raised concerns that the proposal for government “assistance” or “intervention” powers could give it overly broad powers to issue directions or act autonomously.
    AWS is concerned that there isn’t clarity around whether the triggers for exercising such powers are objective and specific, whether or how the government would be able to objectively assess if its directions or assistance would improve the situation, what an entity could be directed to do or not do, what checks and balances would apply, and whether an entity has rights of review and appeal.
    HERE’S MORE More

  • in

    Npm package caught stealing sensitive Discord and browser files

    Security researchers at Sonatype have discovered today an npm package (JavaScript library) that contains malicious code designed to steal sensitive files from a user’s browsers and Discord application.

    techrepublic cheat sheet

    Named discord.dll, the malicious JavaScript library is still available via npm, a web portal, command-line utility, and package manager for JavaScript programmers.
    Developers use npm to load and then update libraries (npm packages) inside their JavaScript projects — may them be websites, desktop apps, or server applications.
    Sonatype says that once installed, discord.dll will run malicious code to search a developer’s computer for certain applications and then retrieve their internal LevelDB databases.
    Targeted apps include browsers like Google Chrome, Brave, Opera, and the Yandex Browser, but also the Discord instant messaging app, popular today with most online gamers.
    The files the malware retrieves are LevelDB databases, which the aforementioned apps use to store information such as browsing histories and various access tokens.
    Discord.dll would read the files and attempt to post their content in a Discord channel (as a Discord webhook).
    Links to another malicious npm package

    Sonatype said that after a review, it found that the malicious code was an improved version of a malicious library it saw in August. Named fallguys, this library, too, was collecting the same information, although in a less complicated manner.
    Sonatype, a company that monitors public package repositories as part of its developer security operations (DevSecOps) services, said discord.dll was published more than five months ago and has been downloaded more than 100 times.
    In contrast, despite being available on the npm portal for only two weeks, the fallguys package was downloaded more than 300 times.
    The reason for the success of the first package can be linked to the fact that fallguys contained a README file advertising the library as an interface to the “Fall Guys: Ultimate Knockout” game API. On the other hand, the discord.dll package contained an empty README, suggesting that the project was either abandoned or never “officially” launched by its creator.
    Other suspicious npm packages detected
    The discord.dll package is still available on the npm portal, but Sonatype said it already notified the npm security team, and the package will most likely be removed in the coming days.
    Furthermore, researchers also said the author of the discord.dll package had also uploaded ten other packages on the npm site, three of which contained malicious behavior that would download and run three mysterious EXE files, a non-standard behavior for JavaScript (npm) packages.
    Since the EXE files could not be retrieved, researchers were unable to fully confirm the nature of the three libraries, named discord.app (88 downloads), ac-addon (46 downloads), and wsbd.js (38 downloads). More

  • in

    Bug hunter wins 'Researcher of the Month' award for DOD account takeover bug

    The US Department of Defense has fixed a severe vulnerability impacting its internal network that would have allowed threat actors to hijack DOD accounts just by modifying a few parameters in web requests sent to DOD servers.
    The vulnerability was discovered by Jeff Steinburg, a security researcher at US security firm Silent Breach, and privately reported and patched via the DOD’s Vulnerability Disclosure Program (VDP).
    The issue received a severity rating of “Critical (9 ~ 10)” because the bug required minimal technical skills to exploit and hijack any DOD account of the attacker’s choosing.
    The severity of the reported issue earned Steinburg the DOD’s “Researcher of the Month” award, despite the bug being the researcher’s first DOD VDP report.

    While some details about the bug have been disclosed earlier today, a full report won’t be fully available; to protect the security of the DOD network.
    According to this summary report, the bug was categorized as an Insecure Direct Object References (IDOR) vulnerability, a bug where security checks are missing from an application, allowing hackers to modify a few parameters without any additional identity checks.
    In the DOD’s case, the bug would have allowed an attacker to take a legitimate web request sent to a DOD website, modify the user ID and username parameters, and the DOD site would have allowed the attacker to change any user’s DOD account password — which would have allowed hackers to hijack accounts and later breach the DOD’s network.

    Today, IDOR bugs are considered easy to find due to the plethora of automated tools that make their discovery a less time-consuming process.
    Most IDOR bugs today allow attackers to modify harmless parameters and tweak account settings of little importance, but some IDOR bugs can also have severe consequences when the IDOR bugs reside in sensitive account fields such as passwords and account recovery/payout emails, or for price values in shopping carts, John Jackson, an Application Security Engineer at Shutterstock, told ZDNet in an interview today.
    “Insecure Direct Object Reference vulnerabilities are those silent, underrated bugs, yet they are not uncommon,” Jackson said.
    The DOD fixed the bug by adding a user session mechanism to the DOD account system, preventing attackers from modifying parameters without authenticating on the site first, or by obtaining an attacked DOD user’s session cookie first. More